This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/57053] inaccurate message for ambiguous calls when in fact there is not valid candidate
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 24 Apr 2013 07:49:59 +0000
- Subject: [Bug c++/57053] inaccurate message for ambiguous calls when in fact there is not valid candidate
- Auto-submitted: auto-generated
- References: <bug-57053-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57053
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-04-24
CC| |manu at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #1 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2013-04-24 07:49:59 UTC ---
I think you are right. There are also other issues with this output: printing
foo(int) as you say is not very helpful, the use of error: for explanatory
notes, and what is "near match"?