public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84849] [DR1228] Ambiguous resolution of braze initializer list to a class with explicit constructors
Date: Wed, 31 May 2023 20:59:52 +0000 [thread overview]
Message-ID: <bug-84849-4-DTBM1HC5cq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-84849-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84849
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Ambiguous resolution of |[DR1228] Ambiguous
|braze initializer list to a |resolution of braze
|class with explicit |initializer list to a class
|constructors |with explicit constructors
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=cwg1228
Status|ASSIGNED |SUSPENDED
Assignee|mpolacek at gcc dot gnu.org |unassigned at gcc dot gnu.org
CC| |jason at gcc dot gnu.org
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
I'm not marking this as a dup of PR60027 because of the specific case of
copy/move constructors, which cannot be constrained to avoid this problem. The
patch in PR109247 fixes the first three testcases, which fall into that
category, but not the testcase in #5, which does not.
The testcase in #6 is unrelated; there is no "explicit".
Unassigning from Marek.
next prev parent reply other threads:[~2023-05-31 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-84849-4@http.gcc.gnu.org/bugzilla/>
2021-12-14 5:55 ` [Bug c++/84849] " pinskia at gcc dot gnu.org
2023-05-31 20:59 ` jason at gcc dot gnu.org [this message]
2023-06-01 3:00 ` [Bug c++/84849] [DR1228] " jason at gcc dot gnu.org
2024-04-23 22:29 ` mpolacek 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-84849-4-DTBM1HC5cq@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).