public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lisyarus at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/89062] class template argument deduction failure with parentheses Date: Thu, 01 Oct 2020 07:08:52 +0000 [thread overview] Message-ID: <bug-89062-4-0TvpGAUH7F@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89062-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89062 Nikita Lisitsa <lisyarus at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisyarus at gmail dot com --- Comment #5 from Nikita Lisitsa <lisyarus at gmail dot com> --- Any updates on this? Can confirm this on all gcc versions from 7.1 to 10.2 (see https://godbolt.org/z/4qnfea). Interestingly, for a variadic-template constructor only the first argument triggers the error, i.e. template <typename T> struct A { A(T) {} }; template <typename T> A(T) -> A<T>; template <typename T> struct B { template <typename ... Args> B(Args const & ...){} }; void test() { B<int> b1(A{0}, A{0}, A{0}); // error B<int> b2(A<int>{0}, A{0}, A{0}); // ok }
next parent reply other threads:[~2020-10-01 7:08 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89062-4@http.gcc.gnu.org/bugzilla/> 2020-10-01 7:08 ` lisyarus at gmail dot com [this message] 2020-10-01 13:35 ` mpolacek at gcc dot gnu.org 2021-06-09 0:46 ` mpolacek at gcc dot gnu.org 2021-07-19 12:49 ` mpolacek at gcc dot gnu.org 2021-08-08 17:10 ` ppalka at gcc dot gnu.org 2021-08-11 19:59 ` cvs-commit at gcc dot gnu.org 2021-08-11 20:03 ` ppalka at gcc dot gnu.org 2021-10-06 15:18 ` avi@cloudius-systems.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-89062-4-0TvpGAUH7F@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).