Oleg Yukhnevich

What kind of `topic-specific` things do you want? Feel free to provide more info, so we will be able to improve samples/examples/documentation.

> I'll check if it could be fixed on the library side I might have a solution here: instead of `js("require(\"path\")")` use `js("eval('require')('path')")`. I'm sure that it works (at least...

Someday I think we will need to migrate to https://github.com/Kotlin/kotlinx-io/issues/131, though, it depends on how well it will interop with ktor and so ktor-io, as this is the main transport...

Just in case, while Dokka Gradle Plugin at this moment doesn't support Gradle Configuration Cache, starting from 1.9.20 we do mark tasks as `notCompatibleWithConfigurationCache` (related fix: https://github.com/Kotlin/dokka/pull/3438) and so disabling...

> would only work for local modules, right? yeah, the provided workaround will work for local modules only. For external modules, similar workaround is possible, but you will need to...

I think, that wrapping `ByteArray` (or `ByteBuffer`) or any other unsafe API for working with `Segment` will be considered in scope of #135

Some observations from looking on API doc: * all functions which accept `Buffer` (or interfaces) also accepts `byteCount` (`readTo`/`readAtMostTo`/`write`) * all functions which accept `ByteArray` also accepts `startIndex` and `endIndex`...

Some questions arise: * can you describe a contract of `await` and `awaitOrThrow` regarding when they may/should throw or return different results? * Also for me naming similar to coroutine...

Note about 1: removing previously published cinterop could be incompatible change in dependency resolution: https://github.com/icerockdev/moko-units/issues/81 (not sure, that there is YouTrack issue about this)

Just speculating and for sure don't know all details, but considering that some day in future: * locks could be implemented in stdlib * there could be some threads support...