public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roma.sandu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107464] New: Expression error in qualified name lookup with lambdas in unevaluated context
Date: Sun, 30 Oct 2022 17:26:23 +0000	[thread overview]
Message-ID: <bug-107464-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107464

            Bug ID: 107464
           Summary: Expression error in qualified name lookup with lambdas
                    in unevaluated context
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: roma.sandu at gmail dot com
  Target Milestone: ---

Created attachment 53795
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53795&action=edit
Minimal bug repro

I've discovered an interesting bug with unevaluated context lambdas. In the
attached examples, trying to instantiate `boo` with a qualified name results in
an expression error. If we instead bring the name `spooky::boo` into the `evil`
namespace with a `using` statement and instantiate `boo` through an unqualified
name, it works as expected. And finally, if one removes the unevaluated context
lambda in `boo`'s definition, it works in all cases.

             reply	other threads:[~2022-10-30 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 17:26 roma.sandu at gmail dot com [this message]
2022-10-30 17:27 ` [Bug c++/107464] " roma.sandu at gmail dot com
2022-10-30 17:29 ` roma.sandu at gmail dot com
2022-10-30 17:41 ` pinskia at gcc dot gnu.org
2024-04-13  8:15 ` pinskia 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-107464-4@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).