Vsevolod Tolstopyatov

I've applied all the proposed suggestions in #3629, will keep you posted regarding further actions

I've run a few out integration tests, so far so good. Our JPMS-related testing capabilities are limited (because we are not really using JPMS ourselves anywhere), so I've published `1.7.0-jpms-preview`...

Merged manually. Thanks!

The problem is not the name but the semantics -- it's unclear whether the underlying coroutine should be launched in an undispatched manner or not. While sounding like an implementation...

I've published `1.7.0-jpms-preview` to `https://maven.pkg.jetbrains.space/public/p/kotlinx-coroutines/maven` repository; if you are relying on JPMS in your project, consider checking it out before JPMS support is released

Fixed by #3621

A very few API are left as `@FlowPreview`, and they are left so intentionally, so closing this one

https://youtrack.jetbrains.com/issue/KTIJ-24102/Change-coroutine-debugger-implementation-to-use-a-new-package issue to keep track of, this is the pre-requisite to split-package removal

FTR: ``` Benchmark Mode Cnt Score Error Units ChannelSinkBenchmark.channelPipeline avgt 5 2.091 ± 0.291 ms/op ChannelSinkBenchmark.channelPipelineOneThreadLocal avgt 5 3.088 ± 0.271 ms/op ChannelSinkBenchmark.channelPipelineTwoThreadLocals avgt 5 5.055 ± 0.318 ms/op ```...

It seems like we only have a question about cleanPrev. As soon as it's addressed (and JVM IR transformer is disabled probably), the PR is good to go