[Bug c++/59056] ambiguous call to function template overloads not diagnosed

2013-11-14 Thread walter.mascarenhas at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59056 --- Comment #9 from Walter Mascarenhas --- 1) I just wrote that Richard's paragraph, IN ITSELF, does not explain why things are as they are. I did not write that there aren't other reasons to justify the standard's decisions. 2) As I wrote, GCC d

[Bug c++/59056] ambiguous call to function template overloads not diagnosed

2013-11-13 Thread richard-gccbugzilla at metafoo dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59056 --- Comment #8 from Richard Smith --- (In reply to Walter Mascarenhas from comment #7) > In itself, Richard's paragraph "Morally, the function should ambiguous... " > implies that the code below is ambiguous. However, it > compiles just fine with

[Bug c++/59056] ambiguous call to function template overloads not diagnosed

2013-11-13 Thread walter.mascarenhas at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59056 --- Comment #7 from Walter Mascarenhas --- In itself, Richard's paragraph "Morally, the function should ambiguous... " implies that the code below is ambiguous. However, it compiles just fine with gcc 4.8.1, because gcc also takes into account the