public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95454] New: type-level nodiscard not applied to constructors Date: Sun, 31 May 2020 17:53:20 +0000 [thread overview] Message-ID: <bug-95454-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95454 Bug ID: 95454 Summary: type-level nodiscard not applied to constructors Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: johelegp at gmail dot com Target Milestone: --- The following does not warn for constructors. See https://godbolt.org/z/BTZwew. ```C++ struct [[nodiscard]] X { int x; X operator+() const { return *this; } }; class [[nodiscard]] Y { int y; public: Y operator+() const { return *this; } }; void f() { X{}; Y{}; X x; +x; Y y; +y; } ```
next reply other threads:[~2020-05-31 17:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-31 17:53 johelegp at gmail dot com [this message] 2021-12-30 16:31 ` [Bug c++/95454] " steve+gcc at tecwec dot eu 2022-07-19 12:10 ` kyrylo.bohdanenko at gmail dot com 2022-07-19 14:33 ` johelegp at gmail dot com 2023-03-21 15:32 ` pinskia 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-95454-4@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).