Those inline functions can really add up... (source)

btw, since https://youtrack.jetbrains.com/issue/KT-53438 debugging through inline functions inside IntelliJ should be reliable. that doesn't help stacktraces though, since the JVM totally ignores SourceDebugExtension (https://bugs.openjdk.org/browse/JDK-4972961)

Yeah, debugging inlines is fine, but the stacktrace thing constantly gets me. Between inlines and coroutines, Kotlin stacktraces are far less ergonomic than I wish they were.

unfortunately I don't expect it to be possible to fix stack traces even with something as invasive as a jvmti agent, given current JVM limitations

image.png

Better to understand those method names, as they can be located more easily.