Vsevolod Tolstopyatov

>Any update on this ? Unfortunately, no. There are two conceptual problems we see here: 1) The name should be concise enough to be usable yet clearly reflect the intent....

I see. Then I got quite a simple question [to everyone interested in this API]: why do you prefer `runCatching` that ignores `CancalletionException` instead of `runCatching` that catches all, but...

Two critical issues: * No TCO in `send` due to a bug in the inliner. Ilmir is figuring it out. If I inline `sendImpl` in `send` manually, TCO kicks in...

Superseded by #3297

Yeah, it's kinda bummer from the maintenance perspective, but it is more transparent for users -- our `master` reflects the latest release, and open issues are one definitely not released...

We tend to avoid changing API stability guarantees in patch releases, esp. if it is a popular API. We'll likely do it in 1.7.0 as we still have to put...

In the future, to avoid doing work in vain, I strongly suggest initiating the discussion as our [contribution guide](https://github.com/Kotlin/kotlinx.coroutines/blob/master/CONTRIBUTING.md) suggests

A short update: the corresponding support of JPMS should land in IDEA 2022.3, so we are ready to proceed with the change. Could you please rebase it on the most...

Also, it seems like some modules cannot be compiled: https://teamcity.jetbrains.com/viewLog.html?buildId=3984907&tab=buildResultsDiv&buildTypeId=KotlinTools_KotlinxCoroutines_Build

@lion7 Is it ready for review or are you still working on it? (I'm not sure if "re-request review" button is available for external contributors, thus the question)