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++/85973] [[nodiscard]] on class shall emit a warning for unused anonymous variable Date: Tue, 21 Mar 2023 15:33:16 +0000 [thread overview] Message-ID: <bug-85973-4-fFyIZK9cVI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85973-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85973 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-03-21 Ever confirmed|0 |1 Summary|[[nodiscard]] shall emit a |[[nodiscard]] on class |warning for unused |shall emit a warning for |anonymous variable |unused anonymous variable Status|UNCONFIRMED |NEW --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced testcase: ``` struct [[nodiscard]] scope_exit { scope_exit(int); }; int main() { scope_exit{0}; } ``` Note if we move the attribute to the constructor, then GCC will error out.
next prev parent reply other threads:[~2023-03-21 15:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85973-4@http.gcc.gnu.org/bugzilla/> 2023-03-21 15:32 ` [Bug c++/85973] [[nodiscard]] " pinskia at gcc dot gnu.org 2023-03-21 15:32 ` pinskia at gcc dot gnu.org 2023-03-21 15:33 ` pinskia at gcc dot gnu.org [this message] 2024-02-29 17:33 ` [Bug c++/85973] [[nodiscard]] on class " mpolacek at gcc dot gnu.org 2024-08-27 0:28 ` pinskia at gcc dot gnu.org 2024-08-27 10:23 ` leonid.satanovsky at gmail dot com
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-85973-4-fFyIZK9cVI@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).