public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106851] New: [modules] Name conflict for exported using-declaration Date: Tue, 06 Sep 2022 13:58:13 +0000 [thread overview] Message-ID: <bug-106851-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106851 Bug ID: 106851 Summary: [modules] Name conflict for exported using-declaration Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Blocks: 103524 Target Milestone: --- $ cat lib.h namespace outer { template<typename T> void any_of(T) { } namespace inner { struct A { }; inline constexpr A any_of; } } $ gcc -c -std=c++23 -fmodules-ts -x c++-header lib.h $ cat lib.cc export module lib; import "lib.h"; export using outer::any_of; export using outer::inner::any_of; $ gcc -c -std=c++23 -fmodules-ts lib.cc lib.cc:6:28: error: ‘constexpr const outer::inner::A outer::inner::any_of’ conflicts with a previous declaration 6 | export using outer::inner::any_of; | ^~~~~~ In module ./lib.h, imported at lib.cc:3: lib.h:2:29: note: previous declaration ‘void outer::any_of(T)’ 2 | template<typename T> void any_of(T) { } | ^~~~~~ lib.cc:1:8: warning: not writing module ‘lib’ due to errors 1 | export module lib; | ^~~~~~ The names are in different scopes, shouldn't they be exported that way too? Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524 [Bug 103524] [meta-bug] modules issue
next reply other threads:[~2022-09-06 13:58 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-06 13:58 redi at gcc dot gnu.org [this message] 2022-09-06 14:15 ` [Bug c++/106851] " johelegp at gmail dot com 2023-11-09 11:20 ` nathanieloshead at gmail dot com 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@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).