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++/101174] New: [12 Regression] CTAD causes instantiation of invalid specialization Date: Wed, 23 Jun 2021 03:41:50 +0000 [thread overview] Message-ID: <bug-101174-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101174 Bug ID: 101174 Summary: [12 Regression] CTAD causes instantiation of invalid specialization Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ppalka at gcc dot gnu.org Target Milestone: --- The following testcase struct S { using type = int; }; template<class T = int, class U = S> struct multiset { using type = typename U::type; multiset(T); multiset(U); }; template<class T> multiset(T) -> multiset<T>; multiset c(42); is rejected by GCC 12 with <stdin>: In instantiation of ‘struct multiset<int, int>’: <stdin>:13:14: required from here <stdin>:5:9: error: ‘int’ is not a class, struct, or union type <stdin>:7:3: error: ‘multiset<T, U>::multiset(U) [with T = int; U = int]’ cannot be overloaded with ‘multiset<T, U>::multiset(T) [with T = int; U = int]’ <stdin>:6:3: note: previous declaration ‘multiset<T, U>::multiset(T) [with T = int; U = int]’
next reply other threads:[~2021-06-23 3:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-23 3:41 ppalka at gcc dot gnu.org [this message] 2021-06-23 4:21 ` [Bug c++/101174] [12 Regression] CTAD causes instantiation of invalid specialization since r12-926 ppalka at gcc dot gnu.org 2021-06-23 15:03 ` [Bug c++/101174] [12 Regression] CTAD causes instantiation of invalid class " ppalka at gcc dot gnu.org 2021-06-23 21:27 ` cvs-commit at gcc dot gnu.org 2021-06-23 21:28 ` ppalka 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-101174-4@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).