Files
kotlin-fork/compiler/testData/debug/stepping/nestedInline.kt
T
Sergej Jaskiewicz 0e3f48314a [JS IR] Improve stepping test executor
Don't search for box function in the generated code;
instead, stop the execution right before calling it.

This makes stepping tests more accurate.
2022-10-27 09:28:05 +00:00

77 lines
1.3 KiB
Kotlin
Vendored

// This is same as kotlin/compiler/testData/codegen/boxInline/smap/smap.kt
// FILE: test.kt
import builders.*
inline fun test(): String {
var res = "Fail"
html {
head {
res = "OK"
}
}
return res
}
fun box(): String {
var expected = test();
return expected
}
// FILE: 1.kt
package builders
inline fun init(init: () -> Unit) {
init()
}
inline fun initTag2(init: () -> Unit) {
val p = 1;
init()
}
//{val p = initTag2(init); return p} to remove difference in linenumber processing through MethodNode and MethodVisitor should be: = initTag2(init)
inline fun head(init: () -> Unit) { val p = initTag2(init); return p}
inline fun html(init: () -> Unit) {
return init(init)
}
// EXPECTATIONS JVM JVM_IR
// test.kt:19 box
// test.kt:7 box
// test.kt:9 box
// 1.kt:41 box
// 1.kt:29 box
// test.kt:10 box
// 1.kt:37 box
// 1.kt:33 box
// 1.kt:34 box
// test.kt:11 box
// test.kt:12 box
// 1.kt:34 box
// 1.kt:35 box
// 1.kt:37 box
// test.kt:13 box
// 1.kt:29 box
// 1.kt:30 box
// 1.kt:41 box
// test.kt:15 box
// test.kt:19 box
// test.kt:21 box
// EXPECTATIONS JS_IR
// test.kt:7 box
// 1.kt:33 box
// 1.kt:36 box
// 1.kt:37 box
// 1.kt:37 box
// 1.kt:41 box
// test.kt:15 box
// test.kt:19 box
// test.kt:21 box