public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103689] New: Overriding spaceship operator when parent class does not define spaceship operator for itself
Date: Mon, 13 Dec 2021 19:21:11 +0000	[thread overview]
Message-ID: <bug-103689-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103689

            Bug ID: 103689
           Summary: Overriding spaceship operator when parent class does
                    not define spaceship operator for itself
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fchelnokov at gmail dot com
  Target Milestone: ---

The following program is ill-formed:
```
#include <compare>

struct A;

struct I {
    virtual std::strong_ordering operator <=>(const A&) const { return
std::strong_ordering::equal; }
};

struct A : I {
    virtual std::strong_ordering operator <=>(const A&) const = default;
};

int main() {
    A a;
    I & i = a;
    return (i <=> a) == 0;
}
```
since I::operator <=>(const I&) const is not defined, so A::operator <=>(const
A&) const must be implicitly deleted, and a deleted method cannot override a
not deleted method from I. This must be a compilation error (as in Clang). 

GCC compiles it fine, but issues a linker error 
```
undefined reference to `A::operator==(A const&) const'
```
Demo: https://gcc.godbolt.org/z/Geoqdo4T8

Related discussion: https://stackoverflow.com/q/70334766/7325599

             reply	other threads:[~2021-12-13 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 19:21 fchelnokov at gmail dot com [this message]
2021-12-13 23:08 ` [Bug c++/103689] " redi 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-103689-4@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).