OK.
Jason
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
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
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 (
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
Hi,
I have another half-baked issue about which I'd like to have some
guidance... In this case too at least the draft patch works and passes
the testsuite.
Essentially, something seems missing in the way we handle operator!
applied to a TEMPLATE_ID_EXPR, whereas the non-template version alre
