public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steve+gcc at tecwec dot eu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95454] type-level nodiscard not applied to constructors
Date: Thu, 30 Dec 2021 16:31:48 +0000	[thread overview]
Message-ID: <bug-95454-4-s7xYxUYN6H@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

Eric Estievenart <steve+gcc at tecwec dot eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steve+gcc at tecwec dot eu

--- Comment #1 from Eric Estievenart <steve+gcc at tecwec dot eu> ---
Indeed, confirming with even simpler code ( https://godbolt.org/z/EPbsfxYcj ):

struct [[nodiscard]] Z {};

void f()
{
    Z{}; // should warn but does not
}

Tested all versions: 11.2, trunk, with -Wall -Wextra -....

This is really a need for modern code, even experienced developpers sometimes
forget the 'lock' in
Lock lock{&mutex};
and this has severe consequences ;-)

  reply	other threads:[~2021-12-30 16:31 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 ` steve+gcc at tecwec dot eu [this message]
2022-07-19 12:10 ` [Bug c++/95454] " 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-s7xYxUYN6H@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).