proposal-async-await

Proposals [0] that made it into ES8 (“what’s new”): * Object.values/Object.entries - https://github.com/tc39/proposal-object-values-entries * String padding - https://github.com/tc39/proposal-string-pad-start-end * Object.getOwnPropertyDescriptors - https://github.com/ljharb/proposal-object-getownpropertydesc... * Trailing commas - https://github.com/tc39/proposal-trailing-function-commas * Async functions - https://github.com/tc39/ecmascript-asyncawait * Shared memory and atomics - https://github.com/tc39/ecmascript_sharedmem The first five have been available via Babel and/or polyfills for ~18 months or so, so they’ve been used for a while now. [0] https://github.com/tc39/proposals/blob/master/finished-propo...

Someone please correct me if I’m wrong, but I’m pretty sure await has to be within an async function [0]. [0] https://github.com/tc39/ecmascript-asyncawait/issues/36

Thanks for this! Also later in that thread is an example to further bring home the point: https://github.com/tc39/ecmascript-asyncawait/issues/88#issu... Solid reasoning, in my opinion.

Reason is mentioned here: https://github.com/tc39/ecmascript-asyncawait/issues/88#issu...

I like the idea, it's a bit like how lazy list processing works, but then applied to promises. However, I don't completely see the appeal as soon as ES6 or ES7 transforms with a tool like Babel are ok for you. ES7 is probably going to have C#-like async/await syntax[0], which takes this problem away entirely and in a much less complicated matter. This syntax works great today with babeljs. And even if you don't dare using experimental ES7 features yet, you can accomplish just about exactly the same with ES6 generators[1]. If you really really need to avoid compiling your code, then I can see the appeal of this "pseudosynchronous" idea, but I do feel that it's much more complex and error prone than setting up a build process instead. [0] https://github.com/lukehoban/ecmascript-asyncawait [1] http://davidwalsh.name/async-generators

could you point to a place where anyone's said that Go, or any other CSP system, are Actor systems? That would be interesting to see. Promises and futures are not actually identical; and they're paradigms, because they are concepts shared across a large number of different languages. 'Async' is the P in CSP, as in C# (called 'async'), and as in ES7 (https://github.com/lukehoban/ecmascript-asyncawait). Hope this helps you.

For context on this, check out PEP 492: https://www.python.org/dev/peps/pep-0492/ It's a really exciting proposal. AFAIK, it'd make Python 3 the first mainstream imperative scripting language to have these async/await concepts built-in (there is a similar proposal for JavaScript/ES7 built on top of generators and promises[1]). While I've commented before about how asyncio is still a bit more nascent than I'd like, I'm really excited to see where the community takes it. [1]: https://github.com/lukehoban/ecmascript-asyncawait

How do you return a result (this function isn't doing so)? I'm guessing getJSON could be returning a Promise but there must be a way to do the same in an async function. EDIT, here's the spec, looks like you can just return: https://github.com/lukehoban/ecmascript-asyncawait

generator = async yield = await Also, async/await themselves have a proposal accepted into ES7: https://github.com/lukehoban/ecmascript-asyncawait

It sounds like they will add support for the same constructs as JS will have in ES7 https://github.com/lukehoban/ecmascript-asyncawait