public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100617] [modules] Exported namespace not visible from outside when the module imports another module that declares the same namespace
Date: Fri, 11 Feb 2022 13:02:42 +0000	[thread overview]
Message-ID: <bug-100617-4-8828CANmyg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100617-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Johel Ernesto Guerrero Peña <johelegp at gmail dot com> ---
(In reply to wang ivor from comment #1)
> A workaround is to create a module that exports only the namespace A and
> 'export import' it in the module 'test1'.

I did that, but it's not enough. See Bug 102524.

I export a `detail` namespace like this to workaround the issue in its parent
namespace:
```C++
export module waarudo.details.workaround_gcc_bug_100617;

export namespace waarudo::detail {

void workaround_gcc_bug_100617() { }

} // namespace waarudo::detail

```

  parent reply	other threads:[~2022-02-11 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 19:42 [Bug c++/100617] New: " amorvincitomnia.iw at gmail dot com
2021-05-16  8:53 ` [Bug c++/100617] " amorvincitomnia.iw at gmail dot com
2022-02-11 12:47 ` asynts+bugs at gmail dot com
2022-02-11 13:02 ` johelegp at gmail dot com [this message]
2024-02-11 14:15 ` nshead 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-100617-4-8828CANmyg@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).