public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113124] g++ should relax designated initialiser rules for trivial classes (read: C structures) and C arrays.
Date: Thu, 11 Jan 2024 22:22:21 +0000 [thread overview]
Message-ID: <bug-113124-4-gcL9ULA2Ge@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113124-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113124
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2024-01-11
CC| |jason at gcc dot gnu.org
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
Doing this for constant initializers for C compatibility makes sense to me.
But it isn't just a matter of adjusting the diagnostic, we would also need to
actually do the sorting to make the initialization work. Still probably not
that much work, but not trivial.
prev parent reply other threads:[~2024-01-11 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 16:17 [Bug c++/113124] New: " adobriyan at gmail dot com
2023-12-23 16:21 ` [Bug c++/113124] " adobriyan at gmail dot com
2023-12-23 16:22 ` adobriyan at gmail dot com
2023-12-23 17:12 ` pinskia at gcc dot gnu.org
2023-12-23 17:15 ` pinskia at gcc dot gnu.org
2023-12-23 17:45 ` pinskia at gcc dot gnu.org
2023-12-27 16:49 ` adobriyan at gmail dot com
2023-12-28 10:32 ` xry111 at gcc dot gnu.org
2023-12-28 11:40 ` adobriyan at gmail dot com
2023-12-28 12:32 ` xry111 at gcc dot gnu.org
2024-01-11 22:22 ` jason at gcc dot gnu.org [this message]
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-113124-4-gcL9ULA2Ge@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).