public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94227] New: ambiguous lookup for nested-name-specifier in using-declaration is not diagnosed Date: Thu, 19 Mar 2020 19:50:11 +0000 [thread overview] Message-ID: <bug-94227-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94227 Bug ID: 94227 Summary: ambiguous lookup for nested-name-specifier in using-declaration is not diagnosed Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: richard-gccbugzilla at metafoo dot co.uk Target Milestone: --- GCC accepts this invalid code: namespace N1 { int &f(); } namespace N2 { struct N1 { float &f(); }; } using namespace N2; int &r = N1::f(); This should be rejected due to ambiguity: the name N1 on the final line is looked up by unqualified lookup, and that lookup is ambiguous between ::N1 and ::N2::N1. But GCC accepts and selects ::N1. (Originally filed as a Clang rejects-valid here: https://llvm.org/PR45216)
next reply other threads:[~2020-03-19 19:50 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-19 19:50 richard-gccbugzilla at metafoo dot co.uk [this message] 2020-03-19 19:58 ` [Bug c++/94227] " mpolacek 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-94227-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: linkBe 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).