Open mosuem opened 11 months ago
Right, that's not a syntax that is supported by the FFI implementation.
It should give a proper error message.
NoSuchMethodError: The method 'call' was called on null.
And definitely not compile to a non-external function-typed field that has a null
value.
@dcharkes is P2 the right priority for this issue?
When defining a method wrongly as such:
The error messages complain about the number of arguments, not about the wrong type:
Unexpected number of FfiNative annotation parameters. Expected x but has y.
The correct syntax for that example would beIf the error messages could point users that way, that would be great.