[PATCH] D27334: [OpenCL] Ambiguous function call.

[Egor Churaev via Phabricator via cfe-commits]

echuraev added a comment.

In https://reviews.llvm.org/D27334#700521, @Anastasia wrote:

> I don't actually. But remembering the follow up discussion:
>  http://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20161205/178846.html
>  and since we have to deviate from the standard C/C++ implementation anyways I am wondering whether modifying overloading resolution is a better way to go?


Yes, I remember this discussion. But we saw this problem in the real OpenCL code and this warning is able to help developer to understand where his code could be ambiguous. Actually, I don't know the modifying overloading resolution is a better way to go or not. Do you have any suggestions how could we notify developer about this potential problem in better way?


https://reviews.llvm.org/D27334