public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112318] Deprecated move ctor does not trigger -Wdeprecated-declarations when creating a std::optional
Date: Tue, 31 Oct 2023 17:21:30 +0000 [thread overview]
Message-ID: <bug-112318-4-4VrrGRJ3ZZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112318-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112318
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2023-10-31
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, the use of the deprecated function occurs in a system header, so it's
suppressed. There's not really anything libstdc++ can do here.
It seems to me that the front-end should consider the context where the
deprecated function is declared as well as where it's used. If the declaration
is not in a system header, then the use in a system header is probably a
template instantiation involving a user's type. In which case, it's not
"system" code, and should trigger the deprecated warning.
next prev parent reply other threads:[~2023-10-31 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:38 [Bug libstdc++/112318] New: " enolan at alumni dot cmu.edu
2023-10-31 16:41 ` [Bug c++/112318] " pinskia at gcc dot gnu.org
2023-10-31 17:21 ` redi at gcc dot gnu.org [this message]
2023-10-31 17:29 ` redi at gcc dot gnu.org
2023-12-13 14:40 ` herring at lanl dot gov
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-112318-4-4VrrGRJ3ZZ@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).