public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/113844] New: inline namespace lookup ambiguity for using
@ 2024-02-09  1:42 ldalessandro at gmail dot com
  0 siblings, 0 replies; only message in thread
From: ldalessandro at gmail dot com @ 2024-02-09  1:42 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 113844
           Summary: inline namespace lookup ambiguity for using
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ldalessandro at gmail dot com
  Target Milestone: ---

namespace a {
      inline namespace b {
          inline int b{};
      }
  }

  using namespace a::b; // gcc & msvc & edg reject, clang accepts

I think that by https://eel.is/c++draft/basic.lookup.udir#1 this using should
be okay, but gcc seems to be considering the a::b::b integer as a candidate,
which feels wrong. Is there somewhere else that makes this ambiguous?

^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2024-02-09  1:42 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-09  1:42 [Bug c++/113844] New: inline namespace lookup ambiguity for using ldalessandro at gmail dot com

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).