Keep track of array types in OptimizationBasicInterpreter
Merging array types with different element types, for example `[Lj/l/String;` and `[Lj/l/Object;`, now produces `[Lj/l/Object;` (instead of `Lj/l/Object;`), which allows for more precise tracking of null values because we assume that AALOAD on a non-array typed value is possible only if that value is null. #KT-54802 Fixed
This commit is contained in:
@@ -1,6 +1,3 @@
|
||||
// IGNORE_BACKEND: JVM
|
||||
// IGNORE_LIGHT_ANALYSIS
|
||||
|
||||
fun box(): String =
|
||||
g(arrayOf("O"))
|
||||
|
||||
@@ -12,4 +9,3 @@ inline fun <T> Array<out T>.f(lambda: (T) -> T): T =
|
||||
|
||||
inline fun <reified T> Array<out T>?.orEmpty0(): Array<out T> =
|
||||
this ?: (arrayOfNulls<T>(0) as Array<T>)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user