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++/64063] Incorrect "ambiguous template specialization" error
Date: Tue, 25 Nov 2014 00:02:00 -0000 [thread overview]
Message-ID: <bug-64063-4-s5gHrEVTaU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64063-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64063
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Apparently EDG instantiates the member function template, which is not what I
wanted:
template<typename T>
struct S
{
void foo(int) { }
template<typename U> void foo(U); // undefined
};
template void S<char>::foo(int); // XXX
"inst.cc", line 8: error: function "S<T>::foo(U) [with T=char, U=int]" cannot
be instantiated -- no template definition was supplied
template void S<char>::foo(int); // XXX
^
Is there no syntax for instantiating the non-template?
next prev parent reply other threads:[~2014-11-25 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 23:35 [Bug c++/64063] New: " redi at gcc dot gnu.org
2014-11-25 0:02 ` redi at gcc dot gnu.org [this message]
2014-11-25 2:38 ` [Bug c++/64063] [DR 1665] " redi at gcc dot gnu.org
2014-11-25 2:43 ` redi at gcc dot gnu.org
2022-01-24 18:19 ` pinskia at gcc dot gnu.org
2022-01-24 19:13 ` pinskia at gcc dot gnu.org
2022-01-24 19:14 ` 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=bug-64063-4-s5gHrEVTaU@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: link
Be 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).