From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 192F83858414; Thu,  9 Nov 2023 11:20:05 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 192F83858414
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1699528805;
	bh=fnpx/m4y5Blt22klEI/bG+SBtHa6jOdpD/yCOaVEiAw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=KXLpyRJ05alGIaY2jjSScPGrt4uT2WPDNc3oUTMKL7ecLyWOmRwWKzwKptZz7oO7F
	 y4L6apjgnt2z9RhOyDWbFKxHPSZbrZ44/I3qCvpn/QDMR14w0Nt4baXadXRd7jPn0r
	 Gp0mejJy5x6ukSk9+b1N0v2R4P80qLpIfBJQwGB4=
From: "nathanieloshead at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106851] [modules] Name conflict for exported
 using-declaration
Date: Thu, 09 Nov 2023 11:20:04 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathanieloshead at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-106851-4-3b4zWlFKR7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

Nathaniel Shead <nathanieloshead at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nathanieloshead at gmail d=
ot com

--- Comment #2 from Nathaniel Shead <nathanieloshead at gmail dot com> ---
This behaviour should be as expected right? The 'using' is trying to bring =
both
names into the same scope (the global namespace), irrespective of the fact =
that
we're also exporting that new declaration. (That is, removing the 'export'
keywords from this test case gives the exact some result.)

That said, perhaps it would be helpful for the error message to point to the
using-declaration it actually conflicts with, rather than the definition th=
at
said using-declaration points to.=