public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107958] Ambiguity with uniform initialization in overloaded operator and explicit constructor
Date: Sat, 03 Dec 2022 18:12:31 +0000	[thread overview]
Message-ID: <bug-107958-4-DN3XExxLWT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107958-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I think GCC and MSVC are correct here:
[over.match.list]/16.3.1.7
. In copy-listinitialization, if an explicit constructor is chosen, the
initialization is ill-formed. [ Note: This differs from
other situations (16.3.1.3, 16.3.1.4), where only converting constructors are
considered for copy-initialization.
This restriction only applies if this initialization is part of the final
result of overload resolution. — end note ]


Even though the note is techincally not part of the standard, it describes why
clang is wrong here. That is the explicit constructors are used too to figure
out the overload and only if there was no ambiguous, it would be considered as
ill-formed.

  parent reply	other threads:[~2022-12-03 18:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03 16:48 [Bug c++/107958] New: " nruslan_devel at yahoo dot com
2022-12-03 17:01 ` [Bug c++/107958] " pinskia at gcc dot gnu.org
2022-12-03 17:05 ` pinskia at gcc dot gnu.org
2022-12-03 17:11 ` pinskia at gcc dot gnu.org
2022-12-03 18:12 ` pinskia at gcc dot gnu.org [this message]
2022-12-03 18:22 ` pinskia at gcc dot gnu.org
2022-12-03 18:46 ` pinskia at gcc dot gnu.org
2022-12-03 18:49 ` pinskia at gcc dot gnu.org
2022-12-03 18:50 ` pinskia at gcc dot gnu.org
2022-12-04  4:19 ` nruslan_devel at yahoo dot com
2022-12-04  4:39 ` nruslan_devel at yahoo dot com

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-107958-4-DN3XExxLWT@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).