Skip to content

Try to distinguish between boxed and primitive types by nullability #39

@Jeffset

Description

@Jeffset

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 vs int).
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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backend:kspRelated to KSP backendperformancePerformance issue/enhancementpriority:minorIssue with minor priority.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions