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++/103809] spurious reporting of structure redefinition Date: Wed, 22 Dec 2021 20:42:31 +0000 [thread overview] Message-ID: <bug-103809-4-6f4ZE8izfZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103809-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103809 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-12-22 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Known to fail| |10.3.0, 11.2.0, 12.0, 9.4.0 Keywords| |rejects-valid --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Confirmed, not a regression. template<typename T> concept Byte = sizeof(T) == 1; template<typename T> concept NotByte = sizeof(T) != 1; namespace priv { template<typename Value> struct Struct {}; } template<Byte T> struct priv::Struct<T> {}; template<NotByte T> struct priv::Struct<T> {}; 103809.C:14:14: error: redefinition of 'struct priv::Struct<T>' 14 | struct priv::Struct<T> {}; | ^~~~~~~~~ 103809.C:11:14: note: previous definition of 'struct priv::Struct<T>' 11 | struct priv::Struct<T> {}; | ^~~~~~~~~
next prev parent reply other threads:[~2021-12-22 20:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-22 18:23 [Bug c++/103809] New: " florin at iucha dot net 2021-12-22 20:42 ` redi at gcc dot gnu.org [this message] 2021-12-23 12:55 ` [Bug c++/103809] wrong reporting of (template) struct redefinition when doing a more constrained template outside of the namespace ppalka 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-103809-4-6f4ZE8izfZ@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).