public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "frrrwww at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55136] New: template class member template explicit instanciation fails if non template overload exists Date: Tue, 30 Oct 2012 10:56:00 -0000 [thread overview] Message-ID: <bug-55136-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55136 Bug #: 55136 Summary: template class member template explicit instanciation fails if non template overload exists Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: frrrwww@gmail.com this code: template <typename T1> struct A { void f(int) {} template<typename T2> void f(T2) {} }; template void A<int>::f<int>(int); fails with: test2.cpp:6:15: error: ambiguous template specialization ‘f<int>’ for ‘void A<int>::f(int)’ test2.cpp:3:10: error: candidates are: void A<T1>::f(int) [with T1 = int] test2.cpp:4:32: error: template<class T2> void A::f(T2) [with T2 = T2; T1 = int] The instanciation should not be ambiguous as the '<int>' should exclude the non template f. Note that: template <typename T1> struct A { void f(int) {} template<typename T2> void f(T2) {} }; template void A<int>::f(int); fails as well, but I am not sufficiently standard savy to tell if this is compliant behaviour.
next reply other threads:[~2012-10-30 10:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-30 10:56 frrrwww at gmail dot com [this message] 2012-10-30 12:22 ` [Bug c++/55136] template class member template explicit instantiation " redi at gcc dot gnu.org 2014-06-26 15:23 ` paolo.carlini at oracle dot com
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-55136-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).