public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dzhioev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96868] C++20 designated initializer erroneous warnings
Date: Thu, 10 Feb 2022 21:15:32 +0000 [thread overview]
Message-ID: <bug-96868-4-S4zYqKR8Pg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96868-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96868
Pavel Sergeev <dzhioev at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dzhioev at gmail dot com
--- Comment #4 from Pavel Sergeev <dzhioev at gmail dot com> ---
(In reply to Jonathan Wakely from comment #3)
> (In reply to Matt Godbolt from comment #2)
> > Thanks: I was confused (as I think will many folks be).
>
> Approximately everybody is confused by -Wmissing-field-initializers which is
> why people probably shouldn't use it.
>
> It specifically says the **initializer** is missing, not that initialization
> is missing. But everybody thinks it's telling them the member is
> uninitialized.
>
> The manual is at least clear:
>
> > the following code causes such a warning, because "x.h" is implicitly zero
>
> Unfortunately it also says:
>
> > This option does not warn about designated initializers
>
> which might be true for C, but not C++. Should it be true for C++?
Do you see any reasons why it shouldn't?
next prev parent reply other threads:[~2022-02-10 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 12:57 [Bug c++/96868] New: " matt at godbolt dot org
2020-09-01 1:11 ` [Bug c++/96868] " mpolacek at gcc dot gnu.org
2020-09-01 2:47 ` matt at godbolt dot org
2021-11-22 9:35 ` redi at gcc dot gnu.org
2022-02-10 21:15 ` dzhioev at gmail dot com [this message]
2022-10-27 14:51 ` pinskia at gcc dot gnu.org
2022-10-29 12:27 ` chfast at gmail dot com
2023-06-08 18:00 ` mpolacek at gcc dot gnu.org
2023-06-09 14:23 ` cvs-commit at gcc dot gnu.org
2023-08-21 17:44 ` roland at gnu dot 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-96868-4-S4zYqKR8Pg@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).