public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlosgalvezp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109642] False Positive -Wdangling-reference with std::span-like classes Date: Fri, 28 Apr 2023 14:08:37 +0000 [thread overview] Message-ID: <bug-109642-4-bGCAw4QGDU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109642-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109642 --- Comment #6 from Carlos Galvez <carlosgalvezp at gmail dot com> --- Sounds great, thanks for the quick response! I believe "-Wall -Wextra" is the "bare minimum" set of warnings for most projects so I'm afraid people might still need to disable it via "-Wno*". Adding some [[gcc::whatever]] attribute sounds like a very interesting approach, I believe Clang has a similar thing. It's not really a blocker since we can just disable it, I'm just sad to have to do it since I believe it's a really good warning to have!
next prev parent reply other threads:[~2023-04-28 14:08 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-27 6:36 [Bug c++/109642] New: " carlosgalvezp at gmail dot com 2023-04-27 7:03 ` [Bug c++/109642] " pinskia at gcc dot gnu.org 2023-04-27 7:09 ` carlosgalvezp at gmail dot com 2023-04-27 15:49 ` mpolacek at gcc dot gnu.org 2023-04-27 19:20 ` carlosgalvezp at gmail dot com 2023-04-28 13:00 ` mpolacek at gcc dot gnu.org 2023-04-28 14:08 ` carlosgalvezp at gmail dot com [this message] 2023-05-02 19:49 ` cvs-commit at gcc dot gnu.org 2023-06-21 18:43 ` pinskia at gcc dot gnu.org 2023-06-21 18:51 ` mpolacek at gcc dot gnu.org 2023-06-21 19:06 ` barry.revzin at gmail dot com 2024-01-17 12:16 ` miro.palmu at helsinki dot fi 2024-01-19 17:35 ` mpolacek at gcc dot gnu.org 2024-01-19 23:32 ` mpolacek at gcc dot gnu.org 2024-01-22 20:52 ` mpolacek at gcc dot gnu.org 2024-01-22 21:16 ` cvs-commit at gcc dot gnu.org 2024-01-30 18:32 ` mpolacek at gcc dot gnu.org 2024-01-30 18:38 ` lopresti at gmail dot com 2024-01-30 18:42 ` mpolacek at gcc dot gnu.org 2024-03-01 20:55 ` cvs-commit at gcc dot gnu.org 2024-05-01 17:18 ` 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-109642-4-bGCAw4QGDU@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).