I'd guess it chooses the implicit string(const char*) constructor and then feeds it a nullptr. I think the plan is to get rid of this in the future with the new

I'd guess it chooses the implicit string(const char*) constructor and then feeds it a nullptr. I think the plan is to get rid of this in the future with the new nullptr_t/nullptr mechanism, but for now we're stuck with it.