Nikolay Lunyak
a9343aeb7d
This inconsistency is present due to not using the `// WITH_STDLIB` in the above tests. When K1 creates the enum, it tries to generate `entries()`, and for that it tries to load `kotlin.enums.EnumEntries`, but this is actually an unresolved reference. K1 silently swallows it, and proceeds. The reason K2 doesn't fail is that in order to generate `entries()` it simply creates the necessary `ConeClassLikeType` with the desired `classId` instead of loading the whole `ClassDescriptor`. The reason we can still observe `$ENTRIES` and `$entries` in K1 is because they are generated during the JVM codegen, and it only checks if the `EnumEntries` language feature is supported. It doesn't check if the `entries` property has really existed in IR (by this time it's expected to have already been lowered to the `get-entries` function - that's why "has ... existed"). The reason why the codegen doesn't fail when working with `kotlin.enums.EnumEntries` is because it creates its own `IrClassSymbol`. ^KT-55840 Fixed Merge-request: KT-MR-8727 Merged-by: Nikolay Lunyak <Nikolay.Lunyak@jetbrains.com>
26 lines
484 B
Kotlin
Vendored
26 lines
484 B
Kotlin
Vendored
// WITH_STDLIB
|
|
// CHECK_CASES_COUNT: function=box count=6
|
|
// CHECK_IF_COUNT: function=box count=1
|
|
|
|
enum class En { A, B, C }
|
|
|
|
fun box(): String {
|
|
var res = ""
|
|
// nullable variable
|
|
val en2: Any? = En.A
|
|
if (en2 is En) {
|
|
when (en2) {
|
|
En.A -> {res += "O"}
|
|
En.B -> {}
|
|
En.C -> {}
|
|
}
|
|
|
|
when (en2 as En) {
|
|
En.A -> {res += "K"}
|
|
En.B -> {}
|
|
En.C -> {}
|
|
}
|
|
}
|
|
|
|
return res
|
|
} |