public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110349] [C++26] P2169R4 - Placeholder variables with no name Date: Fri, 18 Aug 2023 15:01:15 +0000 [thread overview] Message-ID: <bug-110349-4-zoKrFrFqEp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110349-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110349 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #55725|0 |1 is obsolete| | --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 55757 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55757&action=edit gcc14-pr110349-wip.patch Thanks, made some progress with that. I wonder if the paper isn't incomplete though. My understanding of the intent is that say void foo () { auto a = [_ = 1, _ = 2] () {}; } is valid, similarly struct S { int _ = 1; int _ = 2; }; (and it seems the clang implementation allows that), but we still have https://eel.is/c++draft/expr.prim.lambda.capture#2 "Ignoring appearances in initializers of init-captures, an identifier or this shall not appear more than once in a lambda-capture." and https://eel.is/c++draft/class.mem#general-5 "A member shall not be declared twice in the member-specification, except that" and nothing mentioning the name-independent exception in either case. Another thing is we have that https://eel.is/c++draft/basic.scope.block#2 spot which has been changed by the paper, so void baz (int _) { int _ = 1; } void qux () { if (int _ = 2) { int _ = 3; } } etc. cases are valid which have been invalid before, but the important question is if ++_; is allowed after 1; and/or 3; https://eel.is/c++draft/basic.scope.scope#6 has the note: "An id-expression that names a unique name-independent declaration is usable until an additional declaration of the same name is introduced in the same scope ([basic.lookup.general])." but does that apply here? https://eel.is/c++draft/basic.scope.block#2 seems to talk about the behavior in the same scope, but aren't the scopes different here? Seems clang rejects the baz case with ++_; added after 1; (and the WIP patch does too), but doesn't reject ++_; added after 3; (while the WIP patch does).
next prev parent reply other threads:[~2023-08-18 15:01 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-21 16:27 [Bug c++/110349] New: " mpolacek at gcc dot gnu.org 2023-06-22 6:03 ` [Bug c++/110349] " pinskia at gcc dot gnu.org 2023-08-11 15:32 ` jakub at gcc dot gnu.org 2023-08-11 19:08 ` jason at gcc dot gnu.org 2023-08-18 15:01 ` jakub at gcc dot gnu.org [this message] 2023-08-18 15:33 ` jakub at gcc dot gnu.org 2023-08-18 16:14 ` jason at gcc dot gnu.org 2023-08-18 18:34 ` jakub at gcc dot gnu.org 2023-11-30 8:11 ` cvs-commit at gcc dot gnu.org 2023-11-30 8:16 ` jakub 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-110349-4-zoKrFrFqEp@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).