Fork me on GitHub
#core-async
<
2017-05-29
>
val_waeselynck10:05:30

@tbaldridge I believe I saw you mention a compiler transformation on which the go macro is based, but I can't find the reference again, could you post it here?

val_waeselynck10:05:25

Also, do you think the same principle could be used to create 'persistent flow control', i.e rewrite code that uses if, loop and lexical closures and save the program state at some explicit points to be resumed based on external incoming events ?

val_waeselynck10:05:57

the use case is for implementing conversational bots hosted on cloud-likes environments.

noisesmith13:05:24

in scheme they call a function that remembers the calling context it came from a continuation

peeja18:05:49

Is there a reason I'm missing for why async/map takes a collection of channels rather than multiple channels as varargs, like map?