I hope someday channels will be bound to coroutine lifecycles and we no longer need explicitly do coroutineContext[Job]!!.invokeOnCompletion { broadcastChannel.close() }

But you already shouldn't do this

the use case is that one module uses single channel from another module. And that module needs hook to that channel multiple times (in module), and also provides new single channels to other modules.

class Module(inputStream) { 
    val broadcast = inputStream.broadcast()
   // multi usage: launch { broadcast.consumeEach { ... } }
    fun output() = broadcast.openSubscription().map(...)
}

It's all ok with a consumeEach as you said, but it's not ok with channels which is returned by output() function because they are outside of controllable scope of a module

Just use Flow

Using

asFlow

for a

BroadcastChannel

will not solve the issue as a

BroadcastChannel

stays hot while it's not been explicitly closed with

close()

.

@louiscad Yes, you right, I see now The problem of this code is inputStream, not even broadcast channel actually, broadcast channel just used to close input stream, and I'm not really sure that it's correct enough

This is probably related: https://github.com/Kotlin/kotlinx.coroutines/issues/1086