public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/71825] incorrectly rejects valid C++ code with a template class inside a namespace Date: Thu, 09 Dec 2021 01:04:47 +0000 [thread overview] Message-ID: <bug-71825-4-Ohz3RE1qpG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-71825-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71825 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|rejects-valid |accepts-invalid, diagnostic --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- ICC rejects this with: <source>(7): error: class template and template parameter may not have the same name template < class A > struct N::A ^ When struct A is not in a namespace GCC, clang and MSVC all reject it with a similar message. I suspect ICC gets this right really. That is it should be rejected due to the name being the same. In fact if we did: namespace N { template < class A > struct A { }; } GCC, clang and MSVC reject it too.
parent reply other threads:[~2021-12-09 1:04 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-71825-4@http.gcc.gnu.org/bugzilla/>]
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-71825-4-Ohz3RE1qpG@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).