Mads Ager
c3b5b21845
In addition, made the stepping information for constructor calls consistent across JVM_IR and JVM. For JVM_IR that stepping behavior is consistent for enum constructor calls in <clinit> for JVM it is not.
60 lines
878 B
Kotlin
Vendored
60 lines
878 B
Kotlin
Vendored
// FILE: test.kt
|
|
|
|
class A {
|
|
companion object {
|
|
val s: String
|
|
|
|
init {
|
|
s = "OK"
|
|
}
|
|
|
|
val x = x()
|
|
|
|
init { val a = 32 }
|
|
|
|
init {
|
|
val b = 42
|
|
}
|
|
|
|
init
|
|
{
|
|
val c = 43
|
|
}
|
|
}
|
|
}
|
|
|
|
fun x() = ""
|
|
|
|
fun box() {
|
|
A.x
|
|
A.s
|
|
}
|
|
|
|
// JVM backend has extra steps for getX and getS.
|
|
|
|
// LINENUMBERS
|
|
// test.kt:29 box
|
|
// test.kt:7 <clinit>
|
|
// test.kt:8 <clinit>
|
|
// test.kt:9 <clinit>
|
|
// test.kt:11 <clinit>
|
|
// test.kt:13 <clinit>
|
|
// test.kt:15 <clinit>
|
|
// test.kt:16 <clinit>
|
|
// test.kt:17 <clinit>
|
|
// test.kt:19 <clinit>
|
|
// test.kt:21 <clinit>
|
|
// test.kt:22 <clinit>
|
|
// test.kt:11 getX
|
|
// LINENUMBERS JVM
|
|
// test.kt:11 getX
|
|
// LINENUMBERS
|
|
// test.kt:29 box
|
|
// test.kt:30 box
|
|
// test.kt:5 getS
|
|
// LINENUMBERS JVM
|
|
// test.kt:5 getS
|
|
// LINENUMBERS
|
|
// test.kt:30 box
|
|
// test.kt:31 box
|