public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eyalroz1 at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102199] is_default_constructible incorrect for an inner type with NSDMI
Date: Mon, 06 Sep 2021 19:54:55 +0000 [thread overview]
Message-ID: <bug-102199-4-vL2Dy9fgIV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102199-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102199
--- Comment #6 from Eyal Rozenberg <eyalroz1 at gmx dot com> ---
(In reply to Jonathan Wakely from comment #4)
> See PR 96645 and PR 101227
Ok.
But does that explain why defining an explicit constructor cause g++ to accept
the class as default-constructible?
next prev parent reply other threads:[~2021-09-06 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 9:30 [Bug libstdc++/102199] New: " eyalroz1 at gmx dot com
2021-09-04 13:49 ` [Bug c++/102199] " pinskia at gcc dot gnu.org
2021-09-04 14:01 ` pinskia at gcc dot gnu.org
2021-09-04 14:22 ` eyalroz1 at gmx dot com
2021-09-06 15:58 ` redi at gcc dot gnu.org
2021-09-06 19:39 ` eyalroz1 at gmx dot com
2021-09-06 19:54 ` eyalroz1 at gmx dot com [this message]
2021-09-08 10:13 ` redi at gcc dot gnu.org
2022-05-15 7:08 ` pinskia at gcc dot gnu.org
2023-12-03 21:04 ` 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-102199-4-vL2Dy9fgIV@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).