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++/103783] New: Ambiguous overload between constrained static member and unconstrained non-static member
Date: Tue, 21 Dec 2021 01:39:02 +0000	[thread overview]
Message-ID: <bug-103783-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103783
           Summary: Ambiguous overload between constrained static member
                    and unconstrained non-static member
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: barry.revzin at gmail dot com
  Target Milestone: ---

>From StackOverflow (https://stackoverflow.com/q/70429541/2069064):

template<bool b>
struct s {
    void f() const;
    static void f() requires b;
};

void g() {
    s<true>().f();
}

gcc rejects with:

<source>: In function 'void g()':
<source>:8:20: error: call of overloaded 'f()' is ambiguous
    8 |         s<true>().f();
      |         ~~~~~~~~~~~^~
<source>:3:14: note: candidate: 'void s<b>::f() const [with bool b = true]'
    3 |         void f() const;
      |              ^
<source>:4:21: note: candidate: 'static void s<b>::f() requires  b [with bool b
= true]'
    4 |         static void f() requires b;
      |                     ^

I don't think this is an instance of P2113 with non-equivalent templates, seems
like this case should compile. clang and msvc accept.

             reply	other threads:[~2021-12-21  1:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  1:39 barry.revzin at gmail dot com [this message]
2021-12-21  1:50 ` [Bug c++/103783] " pinskia at gcc dot gnu.org
2022-01-02  5:40 ` fchelnokov at gmail dot com
2022-01-02 16:57 ` davidfromonline at gmail dot com
2022-01-02 19:23 ` davidfromonline at gmail dot com
2022-01-04 18:08 ` ppalka at gcc dot gnu.org
2022-01-10 19:59 ` cvs-commit at gcc dot gnu.org
2022-01-10 21:16 ` cvs-commit at gcc dot gnu.org
2022-01-10 21:17 ` 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-103783-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).