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++/106150] [DR 2084] union with more than one variant and non-trivial constructor is not accepted
Date: Wed, 20 Jul 2022 21:31:56 +0000 [thread overview]
Message-ID: <bug-106150-4-PSSPMP3qx2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106150-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106150
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=98423
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> Here is an example which is valid (after
> https://cplusplus.github.io/CWG/issues/2084.html):
> struct S1 {
> S1();
> };
> struct S {
> S();
> };
> union U {
> S s{};
> S1 s1;
> } u;
>
> The check in GCC for this seems to be off, if only the variant s is there,
> GCC (and clang) accepts it.
>
> So the full check for the defect report was never really done (and it was
> not even mentioned in the defect report commentary either).
Yes, all of gcc, clang, edg and msvc reject cases like this.
It should not matter that S1 does not have a trivial default ctor, because the
default member initializer should make this equivalent to:
union U {
S s;
S1 s1;
U() : s() { }
};
Having to write a user-provided constructor is annoying, because to do it
"right" in a generic std::lib template requires:
constexpr U() noexcept(is_nothrow_default_constructible_v<S>) requires
default_initializable<S> { }
But that should be approximately how the defaulted default ctor is defined
automatically, without all that verbosity.
This is a dup of PR 98423, where Jakub pointed out the code that needs to
change, and what needs to happen.
next prev parent reply other threads:[~2022-07-20 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 18:45 [Bug c++/106150] New: Incorrect error for defaulted anonymous union member jens.maurer at gmx dot net
2022-07-01 1:40 ` [Bug c++/106150] " pinskia at gcc dot gnu.org
2022-07-01 1:43 ` pinskia at gcc dot gnu.org
2022-07-01 1:56 ` pinskia at gcc dot gnu.org
2022-07-01 1:58 ` [Bug c++/106150] [DR 2084] union with more than one variant and non-trivial constructor is not accepted pinskia at gcc dot gnu.org
2022-07-01 2:05 ` pinskia at gcc dot gnu.org
2022-07-01 6:20 ` jens.maurer at gmx dot net
2022-07-20 21:31 ` redi at gcc dot gnu.org [this message]
2022-07-22 7:23 ` 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-106150-4-PSSPMP3qx2@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: link
Be 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).