On 07/16/2014 12:39 AM, Paolo Carlini wrote:
In practice, both for the original testcase and for a conditional (and in more cases, eg conditional expressions), what happens is that perform_implicit_conversion_flags is called, which, when implicit_conversion fails, calls instantiate_type (and then resolve_address_of_overloaded_function) only to get a good error message. Thus, would it make sense to use resolve_nondeduced_context in perform_implicit_conversion_flags itself?!? Conservatively, only when the target type is a boolean_type_node, maybe?
How about in standard_conversion in the type_unknown_p case after we've checked for pointer-to(-member)-function?
Jason
