https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104365
--- Comment #5 from Andris Pavenis <andris at gcc dot gnu.org> --- The warning should be in case when both 1) there is preferred standard conversion sequence for parameter of one overloaded method 2) there is other user defined conversion sequences for one more more other overloaded methods Message format could be similar as current ambiguity message only downgraded to warning (maybe preferred conversion sequence could be marked in the message) const char* -> bool and const char* -> std::string could be one example which could likely cause problems I could imagine similar situation with integer number conversion and some extended precision number library.
