public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/88165] error: default member initializer for 'A::B::m' required before the end of its enclosing class Date: Fri, 22 Apr 2022 08:35:10 +0000 [thread overview] Message-ID: <bug-88165-4-ZivF7qr5oo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88165-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88165 --- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Fedor Chelnokov from comment #7) > This struct definition: > ``` > struct A { > struct B { > int i = 0; > B() {} This declares default constructor, meaning that the type is default constructible. Period. By declaring B(); you assert that B is default constructible. > }; > A(B = {}); This is valid, because the user-provided default constructor for B is all the compiler needs to see to know that B={} is valid. > }; > ``` > is accepted by GCC, but another one ({} replaced with = default) is not: > ``` > struct C { > struct D { > int i = 0; > D() = default; This declares a default constructor that might be defined implicitly by the compiler, **or** it might get deleted if the member definitions of D would make the implicit default constructor ill-formed. This is obviously very different from the case where you declare B(); There is no assertion that D is default constructible, the compiler has to deduce whether or not that's true. That depends on the default member initializer for D::i. The initializer (which is just '0' here) is a "complete class context" which means it is not processed until the class D is complete (this allows you to use other members, or e.g. sizeof(D) as the initializer). A nested class like C::D is not complete until its enclosing class is complete. This means the initializer for C::D::i is compiled after C is complete. This means whether C::D is default constructible is not known until C is complete. > }; > C(D = {}); This requires checking whether C::D is default constructible, but we are still in the body of C, so C is not complete, which means C::D is not complete, which means we don't know if C::D is default constructible. > }; > ``` > Demo: https://gcc.godbolt.org/z/WTPdTn1Yf > > Could you please explain why? I though that both must be same accepted or > same rejected. I hope the explanation above helps. GCC trunk now has a tweak to parse simple initializers like 0 immediately, instead of waiting for the class to be complete (because 0 doesn't depend on anything in the class). But for the original example in comment 0 the initializer std::numeric_limits<double>::max(); has to perform name lookup and overload resolution, and so is still delayed until the class is complete.
next prev parent reply other threads:[~2022-04-22 8:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88165-4@http.gcc.gnu.org/bugzilla/> 2021-12-14 5:07 ` pinskia at gcc dot gnu.org 2021-12-14 5:16 ` pinskia at gcc dot gnu.org 2022-01-13 6:55 ` fchelnokov at gmail dot com 2022-04-22 8:18 ` jcl at nvidia dot com 2022-04-22 8:26 ` redi at gcc dot gnu.org 2022-04-22 8:35 ` redi at gcc dot gnu.org [this message] 2022-04-22 8:44 ` fchelnokov at gmail dot com 2022-04-22 8:55 ` jcl at nvidia dot com 2022-04-22 10:29 ` andysem at mail dot ru 2022-04-22 10:42 ` redi 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-88165-4-ZivF7qr5oo@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).