public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113563] Rejects capture of `this` in C++23 `this auto` lambda
Date: Mon, 05 Feb 2024 08:45:24 +0000 [thread overview]
Message-ID: <bug-113563-4-hVWKBrdiWB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113563-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113563
Jiang An <de34 at live dot cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |de34 at live dot cn
--- Comment #1 from Jiang An <de34 at live dot cn> ---
(In reply to Arthur O'Dwyer from comment #0)
> Btw, I do like that GCC eagerly and SFINAE-friendlily rejects `[&](this T)
> {}`. I hope fixing this bug doesn't require undoing that feature.
> (By "SFINAE-friendly" I mean https://godbolt.org/z/fK4f13343 )
> See also
> https://quuxplusone.github.io/blog/2024/01/23/capturing-lambda-deducing-this/
Hmm... after reading CWG2672
(https://cplusplus.github.io/CWG/issues/2672.html), I think the
SFINAE-friendliness is actually required since the parameter list of a lambda
expression is in the immediate context (only the lambda body is excluded).
next prev parent reply other threads:[~2024-02-05 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 17:38 [Bug c++/113563] New: " arthur.j.odwyer at gmail dot com
2024-02-05 8:45 ` de34 at live dot cn [this message]
2024-02-07 14:56 ` [Bug c++/113563] " ppalka at gcc dot gnu.org
2024-02-07 15:00 ` ppalka at gcc dot gnu.org
2024-03-06 19:56 ` ppalka 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-113563-4-hVWKBrdiWB@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: link
Be 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).