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++/101344] braced-init-list not supported in an aggregate deduction Date: Thu, 12 Aug 2021 15:20:58 +0000 [thread overview] Message-ID: <bug-101344-4-vY74RpsTVZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101344-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101344 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot gnu.org CC| |ppalka at gcc dot gnu.org See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=101803 Status|NEW |ASSIGNED --- Comment #2 from Patrick Palka <ppalka at gcc dot gnu.org> --- Another rejects-valid example (I think): template<class T=void> struct C { int m; int t[2]; }; C b{1, {2, 3}}; The relevant wording seems to be https://eel.is/c++draft/over.match.class.deduct#1.5. Rather than only "considering" brace elision for int[2] (and other non-dependent aggregate type), we seem to require it.
next prev parent reply other threads:[~2021-08-12 15:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-06 16:24 [Bug c++/101344] New: " fchelnokov at gmail dot com 2021-07-12 11:02 ` [Bug c++/101344] " redi at gcc dot gnu.org 2021-08-12 15:20 ` ppalka at gcc dot gnu.org [this message] 2021-08-12 15:27 ` [Bug c++/101344] [11/12 Regression] " ppalka at gcc dot gnu.org 2021-08-18 12:39 ` cvs-commit at gcc dot gnu.org 2021-08-18 12:51 ` ppalka at gcc dot gnu.org 2021-09-19 23:17 ` pinskia at gcc dot gnu.org 2021-10-06 14:15 ` cvs-commit at gcc dot gnu.org 2021-10-06 14:18 ` ppalka at gcc dot gnu.org 2021-10-07 6:55 ` fchelnokov at gmail dot 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-101344-4-vY74RpsTVZ@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).