The problem of “waiting forever” in the case of <@...

# coroutines

[elizarov]

The problem of “waiting forever” in the case of @uhe example of is called “communication deadlock”. It is not directly related to coroutines. It can happen with any channel-based communication abstraction, like distributed apps. It is not a big problem in practice if you follow established patterns on structuring your communication pipelines

[uli]

elizarov: i would not call it a dead lock from what @uhe explained. As i understand, the sender is just waiting for a receiver as there is no queue to write the sent payload to.
It is more like an almost regular case of blocking due to back pressure