A modern programming language that makes developers happier.

kotlinlang

<@U0QKGKMKN> Hm… I was too fast to claim it is a bug. It is actually incomplete documentation. Here is the deal: closing a channel sends a _close token_ over it. So the `sendJob` in your example had already sent its element, and then the other one closes a channel, sending a close token _after it_. We cannot just abort the sender, because there maybe a receiver somewhere, that expect first to receive `42` and then to receive a closing signal.