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, 11 Aug 2023 15:32:04 +0000	[thread overview]
Message-ID: <bug-110349-4-udUCcfqLV4@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
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 55725
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55725&action=edit
gcc14-pr110349-wip.patch

I've played with this a little bit so far, but am a little bit stuck.
When lookup_name reports error on ambiguous _ because 2+ declarations with the
_ name are in the same scope (counting function overloads as one obviously),
the error is reported too many times, even from tentative parsing.
And also unsure if it should return error_mark_node in that case or not, if I
return error_mark_node I get some extra error recovery errors as well (though
if the error is avoided during tentative parsing, I guess we have to return
error_mark_node in that case.

  parent reply	other threads:[~2023-08-11 15:32 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 [this message]
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
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-udUCcfqLV4@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).