@elizarov will the

AbstractChannel

APIs stabilize before release? I may have a use for a

Channel

backed by a priority queue but want to re-use as much as possible…

It is unlikely. Most likely we’ll keep all channels experimental for a while after release and stabilize them later

👍

Are there any plans to extract channels from core to a separate module of kotlinx.coroutines?

Would you prefer them to be separate? Currently, we are inclining to keep them in the core library, but use new Kotlin 1.3 feature to mark the corresponding APIs as experimental.

I have Android trauma about library sizes and prefer to separate what can be separated. Channels (together with Actors) API looks like more specialised than other kotlinx-corotuines-core primitives. Again, nothing critical, but I can imagine a lot small or medium projects that would use core primitives to replace threads and callbacks and don’t use Channels and Actors Also this solves problem with experimental part of kotlinx-coroutines-core. You can have only stable APIs and have experimental kotlinx-coroutines-channels library