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 18:34:13 +0000 [thread overview]
Message-ID: <bug-110349-4-Trr5xmWpa2@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 #55757|0 |1
is obsolete| |
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 55759
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55759&action=edit
gcc14-pr110349-wip.patch
Some further progress, with lambda capture handling fixed so that it doesn't
emit the bogus errors and very basic start of non-static data member support.
In that area not really sure what to do, because presumably we want to fail
_ member lookups if it is ambiguous but there is tons of internal lookups
that will likely have to work somehow. And there is the binary search on
member_vec vs. linear search on member_vec vs. field search, and anonymous
aggregates etc.
(In reply to Jason Merrill from comment #6)
> No, it inhabits block/function scope.
Ok, so should block/function scope static structured binding act allow
(multiple) placeholders or should the standard wording be changed even for that
case?
If I disable the last hunk in parser.cc in this patch, then #c6 works, but
void freddy ()
{
static int a[2];
static auto [_, _] = a;
static auto [_, _] = a;
}
fails to assemble as there is _ZNDC1_1_EE emitted twice.
next prev parent reply other threads:[~2023-08-18 18:34 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
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 [this message]
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-Trr5xmWpa2@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).