public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113300] GCC rejects valid program involving explicit and non explicit default constructors Date: Wed, 10 Jan 2024 02:56:48 +0000 [thread overview] Message-ID: <bug-113300-4-uCZTJtnQoG@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 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|GCC rejects valid program |GCC rejects valid program |involving copy list |involving explicit and non |initialization A a = {} of |explicit default |a class with explicit and |constructors |non explicit default | |constructors | See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=84849, | |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=60027 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- https://wg21.link/cwg1228
next prev parent reply other threads:[~2024-01-10 2:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 2:53 [Bug c++/113300] New: " 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 [this message] 2024-01-10 2:59 ` [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 3:03 ` 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-uCZTJtnQoG@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).