This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/16070] print something useful instead of <unresolved overloaded function type>
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 22 Oct 2011 19:53:54 +0000
- Subject: [Bug c++/16070] print something useful instead of <unresolved overloaded function type>
- Auto-submitted: auto-generated
- References: <bug-16070-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16070
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-10-22 19:53:54 UTC ---
(In reply to comment #6)
> so g++ is not as good as clang, but it got closer at GCC 4.7. Perhaps g++ could
> handle better the "unresolved overloaded function type"?
Could that be done by splitting the diagnostic into two? When there is no
implicit conversion sequence for an argument which is an overload set print one
message (like clang's "no overload of 'f'") and otherwise print the existing
message.
> (Gosh! how can clang be that good at this?)
I prefer G++'s error for the second candidate, the process that fails is
template argument deduction, not template argument inference.