Vsevolod Tolstopyatov

@whyoleg that's an interesting suggestion, thanks. We'll consider this; one of the potential benefits is the ability to align documentation between various handlers

I'm closing this as it breaks down into multiple issues -- some of them fixed, some of them are being worked on a separate basis (i.e. #3587), and JVMTI is...

Will be fixed with https://github.com/Kotlin/kotlinx.coroutines/commit/3b22c2783708e6c869db187a913b89e4af4f7613

The fix is available in 1.7.0-Beta

Could you please show before/after on `ChannelSinkBenchmark`?

Nice! I'm looking into that

Nope, it will arrive a bit later in 1.5.0-RC (around a week or two from now)

>Do you have an idea of how a such a parsing strategy might look like? I would strongly avoid relying on the message parsing -- it's intended to be extensive,...

It also opens a road to more advanced parsing capabilities, for example the most recent one: https://github.com/eclipse-vertx/vertx-sql-client/blob/cf176f47c270cffb04df4e47639da440450d4a0e/vertx-sql-client/src/main/java/io/vertx/sqlclient/impl/codec/CommonCodec.java (credit to https://twitter.com/forked_franz/status/1783832904344506820)

Closing as "won't fix", please see https://github.com/Kotlin/kotlinx-io#obsolete-warning