public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "f.heckenbach@fh-soft.de" <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: Sat, 08 Jan 2022 01:06:12 +0000	[thread overview]
Message-ID: <bug-94061-4-yuWSJhRcDE@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

Frank Heckenbach <f.heckenbach@fh-soft.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |f.heckenbach@fh-soft.de

--- Comment #1 from Frank Heckenbach <f.heckenbach@fh-soft.de> ---
I ran into the same problem.

Interestingly, clang also seems to reject it, so maybe it is wrong by the
letter of the standard? Though it would seem strange to me -- after all, when
manually implementing B::operator<=> a protected operator in A will do fine.

I hope someone who knows the standard more intimately can confirm whether
that's so and possibly open a defect report to the standard.

Fun fact: When I independently created a minimal test program, my result was
exactly identical to yours (modulo whitespace), including the names of the
structs. :)

       reply	other threads:[~2022-01-08  1:06 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 [this message]
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
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-yuWSJhRcDE@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: link
Be 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).