You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I don't omit some other rules, there are no more restrictions on what the comparison operator function shall satisfy.
Consider this example:
enum E{};
booloperator==(E,E) = default;
This example directly causes GCC to crash while Clang reports some diagnoses for which I cannot find the corresponding wording in the standard.
The text was updated successfully, but these errors were encountered:
jensmaurer
changed the title
The restriction on what comparison operator function that can be explicitly defaulted
[dcl.fct.def.default] Restrictions on what comparison operator function that can be explicitly defaulted
Mar 8, 2022
jensmaurer
changed the title
[dcl.fct.def.default] Restrictions on what comparison operator function that can be explicitly defaulted
[dcl.fct.def.default] Restrictions on what comparison operator function that can be explicitly defaulted CWG2547
Mar 8, 2022
jensmaurer
changed the title
[dcl.fct.def.default] Restrictions on what comparison operator function that can be explicitly defaulted CWG2547
[dcl.fct.def.default] Restrictions on what comparison operator function can be explicitly defaulted CWG2547
Mar 8, 2022
[dcl.fct.def.default] p1 just states:
If I don't omit some other rules, there are no more restrictions on what the comparison operator function shall satisfy.
Consider this example:
This example directly causes GCC to crash while Clang reports some diagnoses for which I cannot find the corresponding wording in the standard.
The text was updated successfully, but these errors were encountered: