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++/102257] call of overloaded 'tuple' is ambiguous
Date: Thu, 02 May 2024 09:28:31 +0000 [thread overview]
Message-ID: <bug-102257-4-MWR4hzeCZX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102257-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102257
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2024-05-02
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #6)
> (In reply to Andrew Pinski from comment #2)
> > See https://wg21.link/cwg1228 this might be invalid code and GCC is correct
> > in rejecting it.
>
> So dup of PR 84849 ?
This seems more closely related to Bug 113300, i.e. CWG 2856, because this is
about explicit default ctors not explicit copy/move ctors.
prev parent reply other threads:[~2024-05-02 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 13:51 [Bug c++/102257] New: " hewillk at gmail dot com
2021-09-09 17:18 ` [Bug c++/102257] " pinskia at gcc dot gnu.org
2021-09-09 20:34 ` pinskia at gcc dot gnu.org
2021-09-10 3:55 ` hewillk at gmail dot com
2021-09-14 15:31 ` ppalka at gcc dot gnu.org
2024-03-27 13:38 ` redi at gcc dot gnu.org
2024-03-27 13:39 ` redi at gcc dot gnu.org
2024-05-02 9:23 ` redi at gcc dot gnu.org
2024-05-02 9:28 ` 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-102257-4-MWR4hzeCZX@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).