public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amorvincitomnia.iw at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100617] New: [modules] Exported namespace not visible from outside when the module imports another module that declares the same namespace Date: Sat, 15 May 2021 19:42:37 +0000 [thread overview] Message-ID: <bug-100617-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100617 Bug ID: 100617 Summary: [modules] Exported namespace not visible from outside when the module imports another module that declares the same namespace Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: amorvincitomnia.iw at gmail dot com Target Milestone: --- See it live: https://wandbox.org/permlink/1Tgk83eCk7VYm3a3 Minimum code to reproduce the error: //test2.cc export module test2; export namespace A{} //test1.cc export module test1; import test2; export namespace A{ int a = 3; } //prog.cc import test1; void g(){ A::a; } Compile it with: $ g++ "-std=c++20" "-fmodules-ts" "test2.cc" "test1.cc" "prog.cc" Results in error: prog.cc: In function 'void g()': prog.cc:5:5: error: 'A' has not been declared 5 | A::a; | ^ Reproduces in both g++ 11.1.0 and g++ 12.0.0 20210510.
next reply other threads:[~2021-05-15 19:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-15 19:42 amorvincitomnia.iw at gmail dot com [this message] 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 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@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).