Update nullability assertion tests that use newer Java features

This commit is contained in:
Dmitry Petrov
2019-12-27 18:14:20 +03:00
parent d622542824
commit 0e4e5ac287
17 changed files with 17 additions and 5 deletions

View File

@@ -2,6 +2,7 @@
// TARGET_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// FILE: box.kt
import kotlin.test.*

View File

@@ -3,6 +3,7 @@
// IGNORE_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// Note: This fails on JVM (non-IR) with "Fail: should throw on get() in loop header". The not-null assertion is not generated when
// assigning to the loop variable. The root cause seems to be that the loop variable is a KtParameter and

View File

@@ -2,6 +2,7 @@
// TARGET_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// FILE: box.kt
import kotlin.test.*

View File

@@ -26,7 +26,7 @@ public class JImpl implements J {
// Type argument (Int) gets @EnhancedNullability because it is not nullable in overridden Kotlin function.
@Override
public List<Integer> listOfNotNull() {
List<Integer> list = new ArrayList<>();
List<Integer> list = new ArrayList<Integer>();
list.add(42);
list.add(-42);
return list;

View File

@@ -20,7 +20,7 @@ import java.util.*;
public class J {
public static List<Integer> listOfMaybeNullable() {
List<Integer> list = new ArrayList<>();
List<Integer> list = new ArrayList<Integer>();
list.add(42);
list.add(null);
return list;

View File

@@ -20,7 +20,7 @@ import java.util.*;
public class J {
public static List<Integer> listOfMaybeNullable() {
List<Integer> list = new ArrayList<>();
List<Integer> list = new ArrayList<Integer>();
list.add(42);
list.add(-42);
return list;

View File

@@ -2,6 +2,7 @@
// TARGET_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// FILE: box.kt
import kotlin.test.*

View File

@@ -3,6 +3,7 @@
// IGNORE_BACKEND_FIR: JVM_IR
// IGNORE_BACKEND: JVM
// WITH_RUNTIME
// JVM_TARGET: 1.8
// Note: This fails on JVM (non-IR) with "Fail: should throw on get() in loop header". The not-null assertion is not generated when
// assigning to the loop variable. The root cause seems to be that the loop variable is a KtParameter and

View File

@@ -2,6 +2,7 @@
// TARGET_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// FILE: box.kt
import kotlin.test.*

View File

@@ -3,6 +3,7 @@
// IGNORE_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// Note: This fails on JVM (non-IR) with "Fail: should throw on get() in loop header". The not-null assertion is not generated when
// assigning to the loop variable. The root cause seems to be that the loop variable is a KtParameter and

View File

@@ -2,6 +2,7 @@
// TARGET_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// FILE: box.kt
import kotlin.test.*

View File

@@ -3,6 +3,7 @@
// IGNORE_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// Note: This fails on JVM (non-IR) with "Fail: should throw on get()". The not-null assertion is not generated when assigning to the
// variables in the destructuring declaration. The root cause seems to be that

View File

@@ -2,6 +2,7 @@
// TARGET_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// FILE: box.kt
import kotlin.test.*

View File

@@ -23,7 +23,7 @@ import java.util.*;
public class J {
public static List<Integer> listOfMaybeNullable() {
List<Integer> list = new ArrayList<>();
List<Integer> list = new ArrayList<Integer>();
list.add(42);
list.add(null);
return list;

View File

@@ -23,7 +23,7 @@ import java.util.*;
public class J {
public static List<Integer> listOfMaybeNullable() {
List<Integer> list = new ArrayList<>();
List<Integer> list = new ArrayList<Integer>();
list.add(42);
list.add(-42);
return list;

View File

@@ -2,6 +2,7 @@
// TARGET_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// FILE: box.kt
import kotlin.test.*

View File

@@ -3,6 +3,7 @@
// IGNORE_BACKEND: JVM
// IGNORE_BACKEND_FIR: JVM_IR
// WITH_RUNTIME
// JVM_TARGET: 1.8
// Note: This fails on JVM (non-IR) with "Fail: should throw on get()". The not-null assertion is not generated when assigning to the
// variables in the destructuring declaration. The root cause seems to be that