public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100084] New: using enum lookup isn't type-only
Date: Wed, 14 Apr 2021 18:03:43 +0000 [thread overview]
Message-ID: <bug-100084-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100084
Bug ID: 100084
Summary: using enum lookup isn't type-only
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: barry.revzin at gmail dot com
Target Milestone: ---
>From Stack Avarflaw (https://stackoverflow.com/q/67096550/2069064):
namespace A { enum A {}; };
using namespace A;
using enum A;
gcc trunk rejects this lookup as ambiguous, between the namespace A and the
enum A. But our lookup in this context should be type-only, so the namespace A
should not a candidate.
next reply other threads:[~2021-04-14 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 18:03 barry.revzin at gmail dot com [this message]
2021-04-14 18:12 ` [Bug c++/100084] " barry.revzin at gmail dot com
2021-04-14 18:18 ` mpolacek at gcc dot gnu.org
2021-04-15 5:22 ` hewillk at gmail dot com
2021-12-24 21:27 ` 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-100084-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).