public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gawain.bolton at free dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108114] New: Designated initialization of parent class results in error in C++20 mode Date: Wed, 14 Dec 2022 20:06:59 +0000 [thread overview] Message-ID: <bug-108114-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108114 Bug ID: 108114 Summary: Designated initialization of parent class results in error in C++20 mode Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gawain.bolton at free dot fr Target Milestone: --- Created attachment 54095 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54095&action=edit Code accepted with -std=c++17 and rejected with -std=c++20 The attached code generates the following error when compiled with -std=c++20: <source>: In function 'int main()': <source>:11:19: error: either all initializer clauses should be designated or none of them should be 11 | B b{{.a = 0}, .b = 1}; | ^ From my understanding of the C++20 standard (cf. https://eel.is/c++draft/dcl.init.general#nt:brace-or-equal-initializer) this code attached is valid since a designated-initializer-clause may be a braced-init-list. This code has no error or warning about designated initialization with -std=c++17 Clang generates a warning about mixed designated/non-designated initialization, which I believe is not merited, but this is not an error.
next reply other threads:[~2022-12-14 20:07 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-14 20:06 gawain.bolton at free dot fr [this message] 2022-12-14 20:14 ` [Bug c++/108114] " pinskia at gcc dot gnu.org 2022-12-14 20:16 ` pinskia 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-108114-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).