public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "avi at scylladb dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106847] New: deprecated class data member makes the class generate diagnostics even when the member is not used
Date: Tue, 06 Sep 2022 10:33:33 +0000	[thread overview]
Message-ID: <bug-106847-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106847
           Summary: deprecated class data member makes the class generate
                    diagnostics even when the member is not used
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: avi at scylladb dot com
  Target Milestone: ---

A class with a deprecated member:

    struct foo {
        [[deprecated]] bool x;
    };

Cannot be used without lots of noise from the compiler:

    foo make_a_foo() {
        foo f;
        return f;
    }

<source>: In function 'foo make_a_foo()':
<source>:10:12: warning: 'f' is used uninitialized [-Wuninitialized]
   10 |     return f;
      |            ^
<source>:9:9: note: 'f' declared here
    9 |     foo f;
      |         ^
Compiler returned: 0


Although I didn't touch x, the compiler thinks I did. IMO synthesized
constructors (and assignment operators) should suppress the warning and only
explicit access by the user should trigger the warning.

             reply	other threads:[~2022-09-06 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 10:33 avi at scylladb dot com [this message]
2022-09-06 10:33 ` [Bug c++/106847] " avi at scylladb dot com
2022-09-07  8:24 ` rguenth at gcc dot gnu.org
2022-09-08  8:52 ` avi at scylladb 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-106847-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: 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).