Skip to content

update: outdated Java interop compiler option removed #4669

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

Merged
danil-pavlov merged 1 commit into from
Jan 21, 2025
Merged

update: outdated Java interop compiler option removed #4669

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions docs/topics/jvm/java-interop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -304,11 +304,9 @@ class BaseWithBound<T : Number> {}
So passing nullable type as a type argument or type parameter produces a warning.

Annotating type arguments and type parameters works with the Java 8 target or higher. The feature requires that the
nullability annotations support the `TYPE_USE` target (`org.jetbrains.annotations` supports this in version 15 and above).
Pass the `-Xtype-enhancement-improvements-strict-mode` compiler option to report errors in Kotlin code that uses
nullability which deviates from the nullability annotations from Java.
nullability annotations support the `TYPE_USE` target (`org.jetbrains.annotations` supports this in version 15 and above).

> Note: If a nullability annotation supports other targets that are applicable to a type in addition to the `TYPE_USE` target, then
> If a nullability annotation supports other targets that are applicable to a type in addition to the `TYPE_USE` target,
> `TYPE_USE` takes priority. For example, if `@Nullable` has both `TYPE_USE` and `METHOD` targets, the Java method
> signature `@Nullable String[] f()` becomes `fun f(): Array<String?>!` in Kotlin.
>
Expand Down
Loading