public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102049] New: Extend attribute deprecated to allow optional 2nd argument Date: Tue, 24 Aug 2021 20:48:22 +0000 [thread overview] Message-ID: <bug-102049-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102049 Bug ID: 102049 Summary: Extend attribute deprecated to allow optional 2nd argument Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mpolacek at gcc dot gnu.org Target Milestone: --- Clang implements something we don't have: __attribute__((deprecated("message", "replacement"))); which we reject. We probably could allow it for the [[gnu::deprecated]] form too (but not [[deprecated]]). I wonder if we want some tweak that if the replacement argument is an empty string, we don't warn -- this should allow code bases to gradually move away from deprecated functions only when there's an actual replacement. [[gnu::deprecated("insecure", "")]] void f(); // no replacement yet, don't warn [[gnu::deprecated("slow", "add2")]] void add(); // warn, use add2 Does this seem worthwhile?
next reply other threads:[~2021-08-24 20:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-24 20:48 mpolacek at gcc dot gnu.org [this message] 2021-08-24 20:48 ` [Bug c++/102049] " mpolacek at gcc dot gnu.org 2021-08-25 0:30 ` msebor at gcc dot gnu.org 2021-09-21 21:47 ` mpolacek at gcc dot gnu.org 2021-09-25 1:36 ` egallager at gcc dot gnu.org 2021-11-02 20:36 ` mpolacek at gcc dot gnu.org 2021-11-03 3:20 ` egallager 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-102049-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).