From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C5DA03865493; Fri, 18 Aug 2023 18:34:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C5DA03865493 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1692383653; bh=Rmr8Pdvpv5aSl7V3tqqTm0W/z7isTLUtPynev/5gKxM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FT6mX3B1C7xf2GyEEPALAeueJIkFWK1koOaUCc3H5hj5q3dOtWfsR27fgUrIj7iJ2 ZwG56MNuNh/FECSpbHG0VMBKC6kyTnIspnmoViDByRACXZib0qXytxZ7aKg/oXYKr1 5JMMgVHlKyw8rZAjWKCyfUdzNdIqlZkxA8e9h1IU= From: "jakub at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110349 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #55757|0 |1 is obsolete| | --- Comment #7 from Jakub Jelinek --- Created attachment 55759 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D55759&action=3Dedit 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 suppor= t. 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 [_, _] =3D a; static auto [_, _] =3D a; } fails to assemble as there is _ZNDC1_1_EE emitted twice.=