public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97819] Pack expansion in member initializer lists nested with their parameter list got rejected. Date: Thu, 19 Nov 2020 18:41:45 +0000 [thread overview] Message-ID: <bug-97819-4-StB9gsEFR4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97819-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97819 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |mpolacek at gcc dot gnu.org Last reconfirmed| |2020-11-19 --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Shorter test: template <typename... T> struct S : T... { template <typename U, typename... V> S(U u, V... v) : T(u, v...)... {} }; struct R { R(int); }; void h() { S<R>(3); }
next prev parent reply other threads:[~2020-11-19 18:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-13 19:56 [Bug c++/97819] New: " gnaggnoyil at gmail dot com 2020-11-19 18:41 ` mpolacek at gcc dot gnu.org [this message] 2021-08-05 1:00 ` [Bug c++/97819] " pinskia at gcc dot gnu.org 2021-12-08 14:30 ` marxin 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-97819-4-StB9gsEFR4@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).