public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105743] New: Bogus unused but set lambda warning Date: Thu, 26 May 2022 17:04:12 +0000 [thread overview] Message-ID: <bug-105743-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105743 Bug ID: 105743 Summary: Bogus unused but set lambda warning Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: johelegp at gmail dot com CC: johelegp at gmail dot com Target Milestone: --- See https://godbolt.org/z/xq16xac15. ```C++ void f(auto x) { x(0); } void g() { static constexpr auto h = [](...) { }; f([](auto x) { h(x); }); } ``` ``` <source>: In function 'void g()': <source>:3:25: warning: variable 'h' set but not used [-Wunused-but-set-variable] 3 | static constexpr auto h = [](...) { }; | ^ ``` Arguably, `h(x)` could perform ADL on `x`. But perhaps it'd be better to stay silent, like the other compilers.
next reply other threads:[~2022-05-26 17:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-26 17:04 johelegp at gmail dot com [this message] 2022-05-26 18:38 ` [Bug c++/105743] " johelegp at gmail dot com 2022-09-23 16:16 ` 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-105743-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).