Need a better validation when there are native fields in a class (direct or from the super class chain) #12455
Labels
area-vm
Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
type-code-health
Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable
Currently the VM has a check to ensure that there is a native resolver in the library in which classes with native fields are defined. This is a
bit restrictive and we need a better validation scheme.
Maybe we don't predefine NativeFieldWrapper classes and instead have them
be defined by the embedder, the burden of validating then falls on the
embedder.
The text was updated successfully, but these errors were encountered: