public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104512] New: [c++20] consteval constructor does not need to initialize all data members Date: Sat, 12 Feb 2022 09:52:04 +0000 [thread overview] Message-ID: <bug-104512-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104512 Bug ID: 104512 Summary: [c++20] consteval constructor does not need to initialize all data members Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fchelnokov at gmail dot com Target Milestone: --- In the next program struct B has immediate consteval default constructor, which does not initialize i field. Then this constructor is used to make a temporary and its i field remains untouched: ``` struct B { bool b = true; int i; consteval B() {} }; static_assert( B{}.b ); ``` Clang and MSVC are fine with it. But GCC complains: error: 'B{true}' is not a constant expression 7 | static_assert( B{}.b ); | ^ error: 'B()' is not a constant expression because it refers to an incompletely initialized variable Demo: https://gcc.godbolt.org/z/x4n6ezrhT The requirement that "every non-variant non-static data member must be initialized" in constexpr/consteval constructor is removed since c++20. Related discussion: https://stackoverflow.com/a/71085832/7325599
next reply other threads:[~2022-02-12 9:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-12 9:52 fchelnokov at gmail dot com [this message] 2022-02-12 10:02 ` [Bug c++/104512] " pinskia at gcc dot gnu.org 2023-01-19 0:33 ` pinskia at gcc dot gnu.org 2023-01-19 0:34 ` pinskia at gcc dot gnu.org 2023-01-19 1:31 ` 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-104512-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).