public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107255] declaration and definition of a template function which vary in use of concept auto syntax are interpreted as ambiguous overloads
Date: Sat, 15 Oct 2022 13:33:01 +0000	[thread overview]
Message-ID: <bug-107255-4-Bb3x829U0e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107255-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jiang An from comment #1)
> I think two declarations are functionally-equivalent but not equivalent.

Yes, I think you're right. Similarly, these are not equivalent despite looking
superficially the same:

template <class F> requires Foo<F>
void bar(F) {}

template <class F>
void bar(F) requires Foo<F> {}

(Lookup for "Foo" actually considers different scopes in these two cases.)

      parent reply	other threads:[~2022-10-15 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  1:40 [Bug c++/107255] New: ation and definition of a template function which vary in use of concept auto syntax are interpreted as ambiguous overloadsdeclar enolan at alumni dot cmu.edu
2022-10-15  7:00 ` [Bug c++/107255] declaration and definition of a template function which vary in use of concept auto syntax are interpreted as ambiguous overloads de34 at live dot cn
2022-10-15 13:33 ` redi at gcc dot gnu.org [this message]

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-107255-4-Bb3x829U0e@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).