public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/85889] lambda expression can capture structured bindings Date: Thu, 09 May 2024 17:03:48 +0000 [thread overview] Message-ID: <bug-85889-4-HjwDb2E2Pv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85889-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85889 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:46bafd9a6b9b776142e0b1424a6ac02e3a2fd300 commit r15-348-g46bafd9a6b9b776142e0b1424a6ac02e3a2fd300 Author: Marek Polacek <polacek@redhat.com> Date: Fri Mar 1 17:13:02 2024 -0500 c++: lambda capturing structured bindings [PR85889] <https://wg21.link/p1381r1> clarifies that it's OK to capture structured bindings. [expr.prim.lambda.capture]/4 says "The identifier in a simple-capture shall denote a local entity" and [basic.pre]/3: "An entity is a [...] structured binding". It doesn't appear that this was made a DR, so, strictly speaking, we should have a -Wc++20-extensions warning, like clang++. PR c++/85889 gcc/cp/ChangeLog: * lambda.cc (add_capture): Add a pedwarn for capturing structured bindings. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/decomp3.C: Use -Wno-c++20-extensions. * g++.dg/cpp1z/decomp60.C: New test.
next prev parent reply other threads:[~2024-05-09 17:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85889-4@http.gcc.gnu.org/bugzilla/> 2022-11-02 0:21 ` ville.voutilainen at gmail dot com 2022-11-02 0:30 ` ville.voutilainen at gmail dot com 2024-05-09 17:03 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-09 17:05 ` mpolacek 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-85889-4-HjwDb2E2Pv@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).