This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 119a. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
2025-12-20
[Accepted as a DR at the November, 2024 meeting.]
(From submission#600.)
With the introduction of explicit object member functions, therestrictions on operator functions became inconsistent. Subclause12.4.1 [over.oper.general] paragraph 7 specifies:
An operator function shall either
- be a member function or
- be a non-member function that has at least one non-objectparameter whose type is a class, a reference to a class, anenumeration, or a reference to an enumeration.
Talking about non-object parameters in a bullet discussingnon-member functions makes no sense. The following example ought tobe prohibited, for consistency withoperator==(int, int):
struct B { bool operator==(this int, int); operator int() const; };Proposed resolution (approved by CWG 2024-11-22):
Change in 12.4.1 [over.oper.general] paragraph 7 as follows, removingthe bullets:
An operator function shalleither
be a member function orbe a non-member function that hashave atleast onenon-objectfunction parameterorimplicit object parameter whose type is a class, a reference toa class, an enumeration, or a reference to an enumeration.