async/await -> await/async: a simpler, less error-prone async syntax

Florian Bösch pyalot at gmail.com
Thu Dec 7 16:11:23 UTC 2017


I fail to see the increased productiveness by converting:

FunctionExpression => function FunctionSignature Block


To:

FunctionExpression => async function FunctionSignature Block


And the equivalent for the grammar for await. Probably:

UnaryExpression =>
  await RealUnaryExpression

Or something



On Thu, Dec 7, 2017 at 4:18 PM, Naveen Chawla <naveen.chwl at gmail.com> wrote:

> You've lost me. It's not intended to add logic. It's a replacement for
> callbacks, and makes expressing async data flows simpler & more manageable,
> allowing more complex async data flows to be expressed more quickly and be
> less prone to bugs. The `autoasync` `background` concept makes this even
> more so. Retaining all the functionality, increasing rate of productivity.
> That's the whole point.
>
> On Thu, 7 Dec 2017 at 20:36 Florian Bösch <pyalot at gmail.com> wrote:
>
>> On Thu, Dec 7, 2017 at 2:34 PM, Naveen Chawla <naveen.chwl at gmail.com>
>> wrote:
>>
>>> How has using async await made you type more? Can you give an example? I
>>> suspect you're not using it in the way it was intended to be
>>>
>>
>> See example OP pasted. It's nothing but async/await. It doesn't add any
>> semantic, syntactic or logic thing to the code. It could be 4 white-spaces
>> and you'd not loose any meaning.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20171207/0cf4133a/attachment.html>


More information about the es-discuss mailing list