kotlin/compiler/testData/codegen/bytecodeText/coroutines/effectivelyInlineOnly.kt at e7e80be34a193dfbc6b48a87d5ce82d2ff1761c4 - kotlin - Gitea: Git with a cup of tea

jlengrand/kotlin

mirror of https://github.com/jlengrand/kotlin.git synced 2026-05-12 00:21:32 +00:00

Files

pyos 0037d5a7c8 JVM: erase conditional suspension markers from inline-only functions

Otherwise, the generated bytecode is unnecessarily suboptimal in some
(arguably weird) cases.

In the JVM backend, this was an accidental regression in #3260, as I had
not noticed that effectively inline-only functions were handled by a
separate branch in FunctionCodegen. In JVM_IR, I'm pretty sure the
redundant markers have always been there as `isSuspensionPoint` in
ExpressionCodegen never checked for effectively-inline-only-ness.

2020-04-08 12:31:23 +02:00

5 lines

117 B

Kotlin

Vendored

Raw Blame History

 // WITH_COROUTINES
 // TREAT_AS_ONE_FILE
 inline suspend fun <reified T> f(x: suspend () -> T) = x()
 // 0 InlineMarker