Re: [C++ Patch/RFC] PR 50961

2014-07-17 Thread Jason Merrill
OK. Jason

Re: [C++ Patch/RFC] PR 50961

2014-07-17 Thread Paolo Carlini
Hi, On 07/17/2014 02:40 AM, Jason Merrill wrote: 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

Re: [C++ Patch/RFC] PR 50961

2014-07-16 Thread Jason Merrill
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

Re: [C++ Patch/RFC] PR 50961

2014-07-15 Thread Paolo Carlini
Hi, On 07/15/2014 11:46 PM, Jason Merrill wrote: You need to call resolve_nondeduced_context at some point. This doesn't seem to be the right place, since you also want to handle code like "if (foo)". Maybe in resolve_address_of_overloaded_function just before the error? Thanks, that helps (

Re: [C++ Patch/RFC] PR 50961

2014-07-15 Thread Jason Merrill
You need to call resolve_nondeduced_context at some point. This doesn't seem to be the right place, since you also want to handle code like "if (foo)". Maybe in resolve_address_of_overloaded_function just before the error? Jason