public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-106851-4-3b4zWlFKR7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106851-4@http.gcc.gnu.org/bugzilla/>

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

Nathaniel Shead <nathanieloshead at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nathanieloshead at gmail dot 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 that
said using-declaration points to.

  parent reply	other threads:[~2023-11-09 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 13:58 [Bug c++/106851] New: " redi at gcc dot gnu.org
2022-09-06 14:15 ` [Bug c++/106851] " johelegp at gmail dot com
2023-11-09 11:20 ` nathanieloshead at gmail dot com [this message]
2024-02-28 11:10 ` redi at gcc dot gnu.org
2024-03-06 14:31 ` redi at gcc dot gnu.org
2024-03-06 23:59 ` nshead at gcc dot gnu.org
2024-03-07  0:02 ` redi 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-106851-4-3b4zWlFKR7@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).