nullptr is not permitted as ctor argument for jobject like types
jwhpryor opened this issue · comments
nullptr should always be viable for use with jobject and jstring, despite being of type nullptr_t. Proxy definitions need to be updated to allow this.
This is actually not a bug. nullptr_t could map onto multiple signatures making function resolution impossible.
For example, if two separate overloads accepted objects or strings, it would be impossible to differentiate which you wanted (despite both being able to accept null objects).
As such this isn't a bug, but required, at least for strings.