public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-90 at tbilles dot hu" <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 07:42:03 +0000 [thread overview] Message-ID: <bug-94061-4-w7cG7ZuiHX@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 Tibor Billes <gcc-90 at tbilles dot hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gcc-90 at tbilles dot hu --- Comment #5 from Tibor Billes <gcc-90 at tbilles dot hu> --- I ran into this problem, I found a detailed stackoverflow discussion that explains that the standard mandate the derived to base conversion mentioned earlier in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94061#c2 It says that the list of subobjects are "formed by a sequence of derived-to-base conversions, class member access expressions, and array subscript expressions applied to x". (https://timsong-cpp.github.io/cppwp/n4868/class.compare.default#6.sentence-3) I'm not a C++ language lawyer, just wanted to provide additional information for anyone looking for this problem. And yeah, I also wish this would work.. Here is the stackoverflow discussion with all the good references to the specific sections of the standard: https://stackoverflow.com/questions/73055625/deriving-class-with-protected-equality-operator-results-in-deleted-default
next prev parent reply other threads:[~2024-04-24 7:42 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 [this message] 2024-04-24 21:31 ` ppalka at gcc dot gnu.org 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-w7cG7ZuiHX@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).