public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94061] defaulted member operator <=> defined as deleted if a base has protected member operator <=> Date: Wed, 24 Apr 2024 21:31:57 +0000 [thread overview] Message-ID: <bug-94061-4-OcBcjfZ4mU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94061-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94061 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org --- Comment #6 from Patrick Palka <ppalka at gcc dot gnu.org> --- It seems reasonable for this to work but there might be a defect, or at least lack of clarity, in the standard in this situation. http://eel.is/c++draft/class.spaceship#3 specifies how a defaulted <=> is defined, in terms of <=> comparisons of corresponding subobjects. But it's not clear how each of these <=> comparisons is written. If they're always written like operator expressions, e.g. x_i <=> y_i then if x_i / y_i are base class subobjects that have a protected <=>, then such a definition would indeed be ill-formed due to the protected access: https://godbolt.org/z/5h4ednq9 The <=> comparison would need to be written A::operator<=>(b) as mentioned in comment #2 in order for the definition to be valid IIUC?
next prev parent reply other threads:[~2024-04-24 21:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-94061-4@http.gcc.gnu.org/bugzilla/> 2022-01-08 1:06 ` f.heckenbach@fh-soft.de 2022-01-08 16:35 ` ppalka at gcc dot gnu.org 2022-01-08 21:59 ` f.heckenbach@fh-soft.de 2022-04-12 9:07 ` feildel+gccbugzilla@corona-renderer.com 2024-04-24 7:42 ` gcc-90 at tbilles dot hu 2024-04-24 21:31 ` ppalka at gcc dot gnu.org [this message] 2024-04-24 21:32 ` ppalka 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-94061-4-OcBcjfZ4mU@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).