public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102283] Inconsistent/wrong overload resolution when using an initializer list and a defaulted template parameter
Date: Tue, 12 Oct 2021 13:47:08 +0000	[thread overview]
Message-ID: <bug-102283-4-hm6nG3BZsI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102283-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Fedor Chelnokov from comment #0 in PR102691)
> This code is valid:
> ```
> struct Foo {};
> struct Bar {};
> 
> constexpr int Baz(const Foo&) { return 0; }
> constexpr int Baz(Bar&&) { return 1; }
> 
> int main()
> {
>   static_assert( Baz({}) == 1 );
> }
> ```
> Here Baz(Bar&&) must be preferred according to [over.ics.rank]/(3.2), as
> Clang does.

But according to [over.ics.list]/8, isn't the conversion from {} to an
aggregate type a user-defined conversion sequence and not a standard conversion
sequence?  And according to [over.ics.rank]/3.3, two such user-defined
conversion sequences to different types are incomparable.

      parent reply	other threads:[~2021-10-12 13:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 19:06 [Bug c++/102283] New: " dangelog at gmail dot com
2021-09-15 16:16 ` [Bug c++/102283] " ppalka at gcc dot gnu.org
2021-09-15 20:29 ` dangelog at gmail dot com
2021-09-16 13:40 ` ppalka at gcc dot gnu.org
2021-09-16 17:46 ` jason at gcc dot gnu.org
2021-10-01 17:30 ` dangelog at gmail dot com
2021-10-12 13:40 ` ppalka at gcc dot gnu.org
2021-10-12 13:47 ` ppalka 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-102283-4-hm6nG3BZsI@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).