Pure IO through coroutines - sounds quite interesting. The main difference to a thunk like () => A seems to be the capability to send a value to the suspended function. Are Kotlin's coroutines multi-shot, i.e. can you resume them from a certain position more than once?
Hi Iven, not really an expert on the coroutines subject but I think the continuation is just one. The idea with IO anyhow should be to build up a full description of your workflow and run it only once at the border of your application.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Pure IO through coroutines - sounds quite interesting. The main difference to a thunk like
() => A
seems to be the capability to send a value to the suspended function. Are Kotlin's coroutines multi-shot, i.e. can you resume them from a certain position more than once?Hi Iven, not really an expert on the coroutines subject but I think the continuation is just one. The idea with IO anyhow should be to build up a full description of your workflow and run it only once at the border of your application.