If you can't indicate that the arrow itself is async somehow (either by
prefixing it with "deferred" or "async" or using a variant of the arrow
itself, e.g. "~=>"), then you get into the issue Brendan describes when you
allow "await" inside the body.


On Thu, Dec 12, 2013 at 10:07 AM, Kevin Smith <zenparsing at gmail.com> wrote:

>  Banning await here is only a solution if you're also not going to ban an
>> async descriptor on the arrow expression. THAT is the mistake.
>>
>
> Not sure I follow - can you elaborate?  What is an "async descriptor on
> the arrow expression"?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131212/243b2b72/attachment.html>

If you can't indicate that the arrow itself is async somehow (either by
prefixing it with `deferred` or `async` or using a variant of the arrow
itself, e.g. `~=>`), then you get into the issue Brendan describes when you allow `await` inside the body.