Holy crap Swift's async/await proposal using delimited continuation-style control flow:https://gist.github.com/lattner/429b9070918248274f25b714dcfc7619#entering-and-leaving-async-code …
-
-
Replying to @jlongster
Practically I think that means async/await can capture more than just one frame on the stack. Thus it's not just a simple shallow `yield`.
1 reply 0 retweets 9 likes -
Replying to @jlongster
The shallow yield is a feature not a bug. It permits a great deal of local reasons for a relative low cost.
2 replies 0 retweets 1 like -
Replying to @wycats @jlongster
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/ …3 replies 0 retweets 6 likes -
Replying to @wycats @littlecalculist
Yep, seen that. All the points are JS-specific, and I'm saying it was a bad choice for the web
1 reply 0 retweets 3 likes -
WAIT WAIT. I meant I'm NOT saying it was a bad choice for the web... yikes, massive twitter fail
2 replies 0 retweets 4 likes
Replying to @jlongster @littlecalculist
I got it :)
8:14 PM - 17 Aug 2017
0 replies
0 retweets
0 likes
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.