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>
22 lines
303 B
Kotlin
Vendored
22 lines
303 B
Kotlin
Vendored
// WITH_STDLIB
|
|
enum class SimpleEnum {
|
|
A, B, C
|
|
}
|
|
|
|
enum class WithConstructor(val x: String) {
|
|
A("1"), B("2"), C("3")
|
|
}
|
|
|
|
enum class WithEntryClass {
|
|
A {
|
|
override fun foo() {}
|
|
}
|
|
;
|
|
abstract fun foo()
|
|
}
|
|
|
|
annotation class Ann
|
|
|
|
enum class WithAnnotations {
|
|
@Ann A, @Ann B
|
|
} |