public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kuzniar95 at o2 dot pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/93842] generic lambda accesses a variable with with automatic storage duration that wasn't captured by the lambda expression Date: Tue, 16 Jun 2020 16:42:14 +0000 [thread overview] Message-ID: <bug-93842-4-qyJxLHe7aD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93842-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93842 kuzniar95 at o2 dot pl changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #5 from kuzniar95 at o2 dot pl --- Actually everything is done well, my bad, sorry. This code explains what's going on: ------------------- void not_odr_use(char); void odr_use(char&); int main() { constexpr char ch1 = '='; [] { not_odr_use(ch1); }; // compiles [] { odr_use(ch1); }; // doesn't compile and it shouldn't constexpr char ch2 = '='; [](auto) { not_odr_use(ch2); }; // this line doesn't instantiate the template (generic lambda is like a hidden template function) so "ch2" never gets to be used } ------------------- I'm happy to close this and confirm that it isn't a compiler bug.
next parent reply other threads:[~2020-06-16 16:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93842-4@http.gcc.gnu.org/bugzilla/> 2020-06-16 16:42 ` kuzniar95 at o2 dot pl [this message] 2020-06-16 16:47 ` kuzniar95 at o2 dot pl 2020-06-16 17:09 ` kuzniar95 at o2 dot pl 2020-06-16 17:20 ` kuzniar95 at o2 dot pl
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-93842-4-qyJxLHe7aD@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).