public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105200] user-defined operator <=> for enumerated types is ignored Date: Fri, 30 Dec 2022 19:45:51 +0000 [thread overview] Message-ID: <bug-105200-4-EsslskDT4X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105200-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105200 Barry Revzin <barry.revzin at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |barry.revzin at gmail dot com --- Comment #6 from Barry Revzin <barry.revzin at gmail dot com> --- This strikes me as a definite wording issue rather than actual design intent. Patrick is correct as to what the wording says - it says non-member candidate, so the rewritten candidates don't count. But I think really we should also consider rewritten candidates. Clang and MSVC both do - which seems much more in line with expectation and the original design. For class types, you can just provide <=>, but for enums, you have to provide <, >, <=, >=, and <=>?? I'm opening a Core issue for this: https://github.com/cplusplus/CWG/issues/205
next prev parent reply other threads:[~2022-12-30 19:45 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-08 7:35 [Bug c++/105200] New: " falbrechtskirchinger at gmail dot com 2022-04-08 10:12 ` [Bug c++/105200] " jakub at gcc dot gnu.org 2022-04-08 11:31 ` jakub at gcc dot gnu.org 2022-04-08 12:26 ` falbrechtskirchinger at gmail dot com 2022-04-08 12:56 ` ppalka at gcc dot gnu.org 2022-04-13 15:35 ` ppalka at gcc dot gnu.org 2022-12-30 19:45 ` barry.revzin at gmail dot com [this message] 2023-01-01 20:00 ` jens.maurer at gmx dot net 2023-01-01 20:08 ` pinskia at gcc dot gnu.org 2023-02-27 12:26 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-105200-4-EsslskDT4X@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).