public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112926] New: issues with nested lambdas and decltype of uncaptured local variable Date: Fri, 08 Dec 2023 20:38:40 +0000 [thread overview] Message-ID: <bug-112926-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112926 Bug ID: 112926 Summary: issues with nested lambdas and decltype of uncaptured local variable Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ppalka at gcc dot gnu.org Target Milestone: --- Here since the outer lambda has no capture-default, using x outside of an unevaluated operand wouldn't capture it (despite the by-copy capture-default of the inner lambda), so the special case in https://eel.is/c++draft/expr.prim.id.unqual#3 doesn't apply and decltype((x) should be int& not const int&. int main() { int x; [] { [=] { using type = decltype((x)); // should be int& not const int& using type = int&; }; }; }
next reply other threads:[~2023-12-08 20:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-08 20:38 ppalka at gcc dot gnu.org [this message] 2023-12-08 20:42 ` [Bug c++/112926] " ppalka at gcc dot gnu.org 2024-04-13 20:31 ` 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-112926-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).