From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21583 invoked by alias); 22 Feb 2002 10:30:14 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 21512 invoked by uid 61); 22 Feb 2002 10:30:08 -0000 Date: Fri, 22 Feb 2002 02:31:00 -0000 Message-ID: <20020222103008.21511.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mstaley@lanl.gov, nobody@gcc.gnu.org From: nathan@gcc.gnu.org Reply-To: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mstaley@lanl.gov, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org X-Mailer: gnatsweb 2.9.3 Subject: Re: c++/5732: g++ not using return type for overload resolution X-SW-Source: 2002-02/txt/msg00560.txt.bz2 List-Id: 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 void Foo (T1, T2); template typename T1::value_type Foo (T2, T1); http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5732