This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/12164] Unambiguous template reported as ambiguous - sometimes
- From: "bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 4 Sep 2003 20:07:23 -0000
- Subject: [Bug c++/12164] Unambiguous template reported as ambiguous - sometimes
- References: <20030904071337.12164.igodard@pacbell.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12164
bangerth at dealii dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
------- Additional Comments From bangerth at dealii dot org 2003-09-04 20:07 -------
Well, it never worked with gcc. And it fails with icc as well (sorry for the confusion in
my earlier message, this was an operator error -- too many files with similar names
in the same directory :-( ).
Regarding your example, using just typedefs is not enough. if you actually use these
types, then you'll notice that F4 yields the same ambiguity. Your testcase is then essentially
equivalent to mine. Besides, it fails with icc as well.
Your assertion that default arguments are second-class matches is incorrect, IMHO.
W.