This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/5732: g++ not using return type for overload resolution
- From: nathan at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, mstaley at lanl dot gov, nobody at gcc dot gnu dot org
- Date: 22 Feb 2002 10:30:08 -0000
- Subject: Re: c++/5732: g++ not using return type for overload resolution
- Reply-to: nathan at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, mstaley at lanl dot gov, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: g++ not using return type for overload resolution
State-Changed-From-To: closed->analyzed
State-Changed-By: nathan
State-Changed-When: Fri Feb 22 02:30:06 2002
State-Changed-Why:
I think it is a bug. We can't tell until instantiation
time whether the two conflict or not, and as pointed out
T::value_type breaks the instantiation when T == int.
Incidentally, I'll bet you don't get the error if you had
something like
template <typename T1, typename T2>
void Foo (T1, T2);
template <typename T2, typename T1>
typename T1::value_type Foo (T2, T1);
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5732