Channels
#coroutines
- d
Deactivated User
12/24/2016, 5:29 PMand being able to consume from other - e
elizarov
12/24/2016, 5:31 PMOk. Got it. You did not actually "cancel" the first coroutine. It was still suspended at
line.bytesStream.next() - d
Deactivated User
12/24/2016, 5:32 PMhw should I cancel it? - e
elizarov
12/24/2016, 5:32 PMThere is currently no way to abort a coroutine that is suspended on something you don't control. You can throw exception from your own suspending functions, but not from an arbitrary place. - e
elizarov
12/24/2016, 5:33 PMIt's like the same conundrum as with
(you can read the story)Thread.stop - v
vmironov
12/24/2016, 5:33 PM@vmironov has left the channel - e
elizarov
12/24/2016, 5:33 PMIt is hard to design a way to asynchronously terminate a background computation when you don't have cooperation from all the parties involved - d
Deactivated User
12/24/2016, 5:33 PMuhm - d
Deactivated User
12/24/2016, 5:33 PMso it is not possible to do the - e
elizarov
12/24/2016, 5:34 PMLike how would
know that previous invoker ofayncGenerate
is no longer waiting?next - d
Deactivated User
12/24/2016, 5:34 PMval line = withTimeout(moveTimeout) { currentPlayer.readLine() } - d
Deactivated User
12/24/2016, 5:35 PMI thoguth that the try...finally - e
elizarov
12/24/2016, 5:35 PMIt is possible in you consistenly use channels - d
Deactivated User
12/24/2016, 5:35 PMwould allow to - d
Deactivated User
12/24/2016, 5:35 PMbut if it is not finished, at least it is going to be gc'ed? - e
elizarov
12/24/2016, 5:35 PMI'd suggest to go though this tutorial in Go: https://tour.golang.org/concurrency/1 - e
elizarov
12/24/2016, 5:37 PMIt have this nice example on how you timeout waiting on communications (exercise #6) and here is the same code in Kotlin: https://github.com/Kotlin/kotlin-coroutines/blob/master/examples/channel/channel-test-6.kt - d
Deactivated User
12/24/2016, 5:39 PMa colleague explained me channels from erlang - e
elizarov
12/24/2016, 5:39 PMThe try { ... } finally { ...} will catch exceptions that your suspending functions throw. I though you'd want to timeout on read. But are not timing out on read. You want to timeout on asyncGenerate.next and it cannot do that. - d
Deactivated User
12/24/2016, 5:39 PMthat was similar to this (I think if I remember fine) - e
elizarov
12/24/2016, 5:39 PMYes. That is a similar concept - d
Deactivated User
12/24/2016, 5:39 PMI was able to do that before because I was using cancellable Promises - e
elizarov
12/24/2016, 5:39 PMThe key trick is select - e
elizarov
12/24/2016, 5:39 PMSo you can wait on multiple channels at the same time - d
Deactivated User
12/24/2016, 5:40 PMresolve, reject + onCance handler on deferred - e
elizarov
12/24/2016, 5:40 PMSo you can select on a channel with your bytes and on a channel that produces a timeout at the same time - d
Deactivated User
12/24/2016, 5:40 PMbut if the read is waiting - d
Deactivated User
12/24/2016, 5:40 PMok I will read first - d
Deactivated User
12/24/2016, 5:40 PMmaybe I would say something stupid 🙂 - e
elizarov
12/24/2016, 5:40 PMInstead using
toyield
, yourasyncGenerate
willread
bytes to channels.send