Daniil Ovchinnikov

I hate to bring it up here, but this is where Loom is expected to shine. Basically, the coroutine library implementation on top of Loom should spawn a new virtual...

In IJ there is little to zero value in `CoroutineId`; we advise to use `CoroutineName` explicitly instead

I'd also like to request a switch to include `CoroutineName` to `toString` representation of `AbstractCoroutine` (`CoroutineId` is not needed). At the moment our coroutine dump has to do it manually,...

This is continuation of https://github.com/Kotlin/kotlinx.coroutines/issues/814#issuecomment-1457747716

> So, here is the problem: how do we carefully migrate from today's state to this ideal future state? We need to somehow start giving a warning on any code...

Basically, yes.

The important thing here is a conceptual problem: should `runBlocking` steal tasks from a limited dispatcher, a thread of which is blocked by the said `runBlocking`? I believe that if...

> Are you considered to use your own dispatcher with a proper thread pool? We considered own dispatcher with proper priority queue, but we cannot forbid everybody else to use...

Related https://github.com/Kotlin/kotlinx.coroutines/issues/3633

3rd approach is now [used in IntelliJ](https://github.com/JetBrains/intellij-community/blob/3571f1c2b660d9c6eb86637bf06f36ca9d044e8f/platform/core-api/src/com/intellij/util/coroutines.kt#L23) https://github.com/Kotlin/kotlinx.coroutines/issues/3505