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++/42018] Template specialization in wrong namespace accepted if it matches template arguments of an earlier specialization Date: Fri, 01 Oct 2010 12:01:00 -0000 [thread overview] Message-ID: <20101001120100.EF7A4Hz0hqNoyhj2qLeoyFHaHerRSmMVBE8JmUWSFVA@z> (raw) In-Reply-To: <bug-42018-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42018 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Accepts definition for |Template specialization in |non-anonymous specialized |wrong namespace accepted if |template method within |it matches template |anonymous namespace |arguments of an earlier | |specialization --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2010-10-01 12:00:51 UTC --- It doesn't even depend on unnamed namespaces! This is also accepted: template<typename> void foo(void); template<> void foo<int>(void); namespace xxx { template<> void foo<int>(void) { return; } } I've adjusted the summary accordingly.
next prev parent reply other threads:[~2010-10-01 12:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-42018-4@http.gcc.gnu.org/bugzilla/> 2010-10-01 11:52 ` [Bug c++/42018] Accepts definition for non-anonymous specialized template method within anonymous namespace redi at gcc dot gnu.org 2010-10-01 12:01 ` redi at gcc dot gnu.org [this message] 2010-10-01 21:21 ` [Bug c++/42018] Template specialization in wrong namespace accepted if it matches template arguments of an earlier specialization redi at gcc dot gnu.org 2021-08-23 8:31 ` pinskia at gcc dot gnu.org 2021-08-23 8:33 ` pinskia 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=20101001120100.EF7A4Hz0hqNoyhj2qLeoyFHaHerRSmMVBE8JmUWSFVA@z \ --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).