On 11/24/2014 01:55 PM, Paolo Carlini wrote:
in this rejects-valid, as part of build_user_type_conversion_1, standard_conversion is called by implicit_conversion with a *null* expr, thus the condition in standard_conversion/* [conv.ptr] A null pointer constant can be converted to a pointer type; ... A null pointer constant of integral type can be converted to an rvalue of type std::nullptr_t. */ if ((tcode == POINTER_TYPE || TYPE_PTRMEM_P (to) || NULLPTR_TYPE_P (to)) && expr && null_ptr_cst_p (expr)) conv = build_conv (ck_std, to, conv); is false and the snippet is rejected. Should we pass a nullptr_node as expr in such cases, ie, when handling conversions functions returning std::nullptr_t?!?
I'd prefer to change the test quoted above to not require expr to be non-null in the case of NULLPTR_TYPE_P.
Jason
