Holy crap Swift's async/await proposal using delimited continuation-style control flow:https://gist.github.com/lattner/429b9070918248274f25b714dcfc7619#entering-and-leaving-async-code …
-
-
There's a great post by
@littlecalculist on this from 2011:http://calculist.org/blog/2011/12/14/why-coroutines-wont-work-on-the-web/ … -
Yep, seen that. All the points are JS-specific, and I'm saying it was a bad choice for the web
-
WAIT WAIT. I meant I'm NOT saying it was a bad choice for the web... yikes, massive twitter fail
-
I got it :)
End of conversation
New conversation -
-
-
I think you get most of the same local reasoning features by expressing async in the type system and requiring yield points to be annotated, irrespective of whether the underlying implementation mechanism is shallow or deep
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.