A modern programming language that makes developers happier.

kotlinlang

Is there any reason stacktrace recovery is <https://github.com/Kotlin/kotlinx.coroutines/blob/fed40ad1f9942d1b16be872cc555e08f965cf881/kotlinx-coroutines-core/native/src/Exceptions.kt#L35|unconditionally disabled> on native targets? It’s not in the `kotlinx-coroutines-debug` module which is JVM only. Is there a big performance penalty on native for this?

The <https://github.com/Kotlin/kotlinx.coroutines/blob/master/docs/topics/debugging.md#stacktrace-recovery-machinery|documentation> about stacktrace recovery also doesn’t make it clear that it’s only available on JVM. The only bit that’s mentioned in the docs which hints at this is the following:

> <https://github.com/Kotlin/kotlinx.coroutines/blob/master/kotlinx-coroutines-debug|kotlinx-coroutines-debug> module provides one of the most powerful debug capabilities in `kotlinx.coroutines`.
> This is a separate module with a *JVM agent*……
But since stacktrace recovery is implemented in the core module it’s not clear to me if it should be available on other targets or not.

It's not disabled, it's just not implemented. There's neither `setStackTrace` (which would allow overwriting the stack trace) on Kotlin/Native nor (to my knowledge) enough reflection capabilities there to allow creating a copy of an exception.

Is there any way the documentation can be clarified?

Sure: <https://github.com/Kotlin/kotlinx.coroutines/issues/4339>