KT-36336 @EnhancedNullability and null checks
Don't insert implicit null check on a value of @EnhancedNullability type used where @EnhancedNullability type is expected. This uncovers a bunch of other problems in FE and BE. KT-36343 and KT-36347 are bugs in StrictJavaNullabilityAssertions implementation which should most likely be fixed in next major language version (with proper breaking change notice). KT-36344 is a design problem which should be addressed after 1.4 issues are resolved.
This commit is contained in:
Vendored
+4
-1
@@ -1,6 +1,6 @@
|
||||
// !LANGUAGE: +StrictJavaNullabilityAssertions
|
||||
// TARGET_BACKEND: JVM
|
||||
// IGNORE_BACKEND: JVM
|
||||
// IGNORE_BACKEND: JVM, JVM_IR
|
||||
// IGNORE_BACKEND_FIR: JVM_IR
|
||||
// WITH_RUNTIME
|
||||
// JVM_TARGET: 1.8
|
||||
@@ -10,6 +10,9 @@
|
||||
// CodegenAnnotatingVisitor/RuntimeAssertionsOnDeclarationBodyChecker do not analyze the need for not-null assertions on KtParameters.
|
||||
// See KT-35698.
|
||||
|
||||
// Note: this fails on JVM_IR because of KT-36343.
|
||||
// It requires potentially breaking changes in FE, so please, don't touch it until the language design decision.
|
||||
|
||||
// FILE: box.kt
|
||||
import kotlin.test.*
|
||||
|
||||
|
||||
Reference in New Issue
Block a user