* Sam Tobin-Hochstadt wrote:
>I don't see what the point of `await` is in your gist.  It looks like
>all of the work is being done by `function^`, which looks to be sugar
>for creating a function and passing it to a scheduler like `Q.async`
>or `taskjs.spawn`.  We could add that sugar if we wanted, and not need
>to add `await`.

The only language construct that allows yielding control until resumed
later so far is `yield`, but using `yield` to `wait` is rather awkward.
-- 
Björn Höhrmann · mailto:bjoern at hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

Sam Tobin-Hochstadt wrote:
>I don't see what the point of `await` is in your gist.  It looks like
>all of the work is being done by `function^`, which looks to be sugar
>for creating a function and passing it to a scheduler like `Q.async`
>or `taskjs.spawn`.  We could add that sugar if we wanted, and not need
>to add `await`.

The only language construct that allows yielding control until resumed
later so far is `yield`, but using `yield` to `wait` is rather awkward.