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++/102257] call of overloaded 'tuple' is ambiguous Date: Tue, 14 Sep 2021 15:31:23 +0000 [thread overview] Message-ID: <bug-102257-4-DteawkNETu@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 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ppalka at gcc dot gnu.org --- Comment #4 from Patrick Palka <ppalka at gcc dot gnu.org> --- (In reply to 康桓瑋 from comment #3) > (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. > > Maybe. But why does GCC accept the following? > > #include <tuple> > #include <string> > > int main() { > std::tuple<std::string, int> t{{}, {}}; > } > > https://godbolt.org/z/ePovjh3fa Looks like we accept this testcase because the template parameter _Alloc for the template candidate template<typename _Alloc, _ImplicitDefaultCtor<is_object<_Alloc>::value, _T1, _T2> = true> tuple(std::allocator_arg_t, const _Alloc&) is no longer deducible (whereas in the original testcase _Alloc is deduced to int here), so this candidate is discarded and the result of overload resolution is no longer ambiguous. (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. Agreed FWIW
next prev parent reply other threads:[~2021-09-14 15:31 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 [this message] 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
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-DteawkNETu@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: linkBe 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).