public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jlame646 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113300] GCC rejects valid program involving copy list initialization A a = {} of a class with explicit and non explicit default constructors
Date: Wed, 10 Jan 2024 02:59:55 +0000 [thread overview]
Message-ID: <bug-113300-4-wSjAWQ4xYC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113300-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113300
Jason Liam <jlame646 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|GCC rejects valid program |GCC rejects valid program
|involving explicit and non |involving copy list
|explicit default |initialization A a = {} of
|constructors |a class with explicit and
| |non explicit default
| |constructors
--- Comment #3 from Jason Liam <jlame646 at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> There is a C++ defect report in this area even ...
Can you post a link to the DR that you're referencing? Or are you referring to
this https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0398r0.html
next prev parent reply other threads:[~2024-01-10 2:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 2:53 [Bug c++/113300] New: GCC rejects valid program involving " jlame646 at gmail dot com
2024-01-10 2:55 ` [Bug c++/113300] " pinskia at gcc dot gnu.org
2024-01-10 2:56 ` pinskia at gcc dot gnu.org
2024-01-10 2:59 ` jlame646 at gmail dot com [this message]
2024-01-10 3:03 ` [Bug c++/113300] GCC rejects valid program involving copy list initialization A a = {} of a class with " jlame646 at gmail dot com
2024-01-10 18:59 ` mpolacek at gcc dot gnu.org
2024-01-30 16:15 ` mpolacek at gcc dot gnu.org
2024-04-23 22:34 ` mpolacek 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-113300-4-wSjAWQ4xYC@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).