Nice article. I think this is similar to the way Kotlin implements coroutine. I believe Kotlin goes to the extra miles to also capture parts of the stack fram

Nice article. I think this is similar to the way Kotlin implements coroutine. I believe Kotlin goes to the extra miles to also capture parts of the stack frames when creating the Continuation object so even when the runtime resume the continuation, the exceptions thrown later get the "correct" stack trace (not the one that shows that you come from a call through a MethodHandle).