public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kyrylo.bohdanenko at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95454] type-level nodiscard not applied to constructors
Date: Tue, 19 Jul 2022 12:10:15 +0000	[thread overview]
Message-ID: <bug-95454-4-u8XZmLOeai@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95454-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95454

Kyrylo Bohdanenko <kyrylo.bohdanenko at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kyrylo.bohdanenko at gmail dot com

--- Comment #2 from Kyrylo Bohdanenko <kyrylo.bohdanenko at gmail dot com> ---
Still relevant as of the current trunk.

A workaround would be to declare the constructor(s) [[nodiscard]]:

struct Data {
    [[nodiscard]] Data() {}
};

int main() {
    Data{};
}

This actually issues a warning:

<source>: In function 'int main()':
<source>:6:11: warning: ignoring return value of 'Data::Data()', declared with
attribute 'nodiscard' [-Wunused-result]

Sandbox: https://godbolt.org/z/3Koj8rra7

  parent reply	other threads:[~2022-07-19 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31 17:53 [Bug c++/95454] New: " johelegp at gmail dot com
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 [this message]
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-u8XZmLOeai@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).