Holy crap Swift's async/await proposal using delimited continuation-style control flow:https://gist.github.com/lattner/429b9070918248274f25b714dcfc7619#entering-and-leaving-async-code …
Function boundaries aren't so good: let depth = 0; function render(c) { depth++; exec(() => c.render()); depth--; }
-
-
If you're using shared mutable state, yes you need to be careful. On the other hand, now you need to re-implement everything as async (.map)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Think about functions like forEach which are expected to be executed synchronously.
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.