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>
45 lines
702 B
Kotlin
Vendored
45 lines
702 B
Kotlin
Vendored
// WITH_STDLIB
|
|
// MODULE: lib
|
|
// FILE: 1.kt
|
|
|
|
import kotlin.reflect.*
|
|
|
|
annotation class Anno(
|
|
val k: KClass<*>,
|
|
val e: C.NestedEnum,
|
|
val a: C.NestedAnno,
|
|
)
|
|
|
|
annotation class AnnoWithDefault(val k: KClass<*> = Nested0::class) {
|
|
class Nested0
|
|
}
|
|
|
|
class C {
|
|
class Nested1
|
|
|
|
enum class NestedEnum { E }
|
|
|
|
annotation class NestedAnno(val k: KClass<*>) {
|
|
class Nested2
|
|
}
|
|
}
|
|
|
|
interface I {
|
|
@Anno(
|
|
C.Nested1::class,
|
|
C.NestedEnum.E,
|
|
C.NestedAnno(C.NestedAnno.Nested2::class),
|
|
)
|
|
@AnnoWithDefault
|
|
fun foo(): String = "OK"
|
|
}
|
|
|
|
// MODULE: main(lib)
|
|
// FILE: 2.kt
|
|
|
|
class D : I {
|
|
fun box(): String = foo()
|
|
}
|
|
|
|
fun box(): String = D().box()
|