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>
30 lines
504 B
Kotlin
Vendored
30 lines
504 B
Kotlin
Vendored
// WITH_STDLIB
|
|
enum class Color(val rgb : Int) {
|
|
RED(0xFF0000),
|
|
GREEN(0x00FF00),
|
|
BLUE(0x0000FF)
|
|
}
|
|
|
|
enum class Direction {
|
|
NORTH,
|
|
SOUTH,
|
|
WEST,
|
|
EAST
|
|
}
|
|
|
|
fun bar(c: Color) = when (c) {
|
|
Color.RED -> 1
|
|
Color.GREEN -> 2
|
|
Color.BLUE -> 3
|
|
}
|
|
|
|
fun foo(d: Direction) = when(d) {
|
|
Direction.NORTH -> 1
|
|
Direction.SOUTH -> 2
|
|
Direction.WEST -> 3
|
|
Direction.EAST -> 4
|
|
}
|
|
|
|
fun box() : String =
|
|
if (foo(Direction.EAST) == 4 && bar(Color.GREEN) == 2) "OK" else "fail"
|