Try to distinguish between boxed and primitive types by nullability #39
Labels
backend:ksp
Related to KSP backend
performance
Performance issue/enhancement
priority:minor
Issue with minor priority.
In order to correctly override methods in Java code in KSP mode, Yatagan uses KSP's experimental APIs to obtain JVM signatures to distinguish between boxed/unboxed java types (e.g.
java.lang.Integer
vsint
).As per google/ksp#870 (comment), there can be no need for that, nullability info alone may be sufficient to make the distinction.
Let's give it a shot. If it's indeed possible, removing cumbersome JVM-signature obtaining/parsing will greatly simplify the implementation while likely improving performance.
The text was updated successfully, but these errors were encountered: