Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kotlin extractor: use special <nulltype> for null literals #17890

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Kotlin extractor: use special <nulltype> for null literals #17890

wants to merge 2 commits into from

Commits on Nov 1, 2024

  1. Kotlin extractor: use special <nulltype> for null literals 

    This matches the Java extractor's treatment of these literals, and so enables dataflow type-tracking to avoid special-casing Kotlin. Natively, Kotlin would regard this as kotlin.Nothing?, the type that can only contain null (kotlin.Nothing without a ? can take nothing at all), which gets Java-ified as java.lang.Void, and this will continue to be used when a null type has to be "boxed", as in representing substituted generic constraints with no possible type.
    @smowton
    smowton committed Nov 1, 2024
    Configuration menu
    Copy the full SHA
    5d3f723 View commit details
    Browse the repository at this point in the history

  2. Be explicit about Kotlin database type

    @smowton
    smowton committed Nov 1, 2024
    Configuration menu
    Copy the full SHA
    81ff394 View commit details
    Browse the repository at this point in the history