As you might already know, MSVC 14 (Visual Studio 2015) is in its
testing phase currently. I stumbled upon a bug report that caught my
The author of this report complains that in the given example he
attached (http://pastebin.com/R5z88xcf) the call to function 'f'
should be unambiguous (MSVC 14 thinks otherwise) according to 22.214.171.124
paragraph 10 in the standard. In response, Visual C++ developer
Jonathan Caves argues that: "[126.96.36.199] has been recently re-written
as the result of a defect report against the C++ language [...]
[...] So partial ordering fails and the function call is ambiguous."
Compiling the example in question (http://pastebin.com/R5z88xcf),
clang 3.5 and 3.6 think the call to f is unambiguous, MSVC14 thinks
it's ambiguous. My question is: which compiler is right about this?