This repository has been archived by the owner on Aug 29, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 46
for await #132
Comments
This comment has been minimized.
This comment has been minimized.
syg
added a commit
to syg/proposal-top-level-await
that referenced
this issue
Oct 7, 2019
Closes tc39#132 Note that `await` in module contexts is always a keyword, so the "Contains `await`" static semantics in this patch will never match an `await` identifier.
MylesBorins
pushed a commit
that referenced
this issue
Oct 23, 2019
Closes #132 Note that `await` in module contexts is always a keyword, so the "Contains `await`" static semantics in this patch will never match an `await` identifier.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Confirming that it is intended that
for await
is also available at module top level, in addition to AwaitExpression.I see no reason that this should not be the case, so it seems the case that step 12 of ParseModule needs to be patched to be aware of
for await
.The text was updated successfully, but these errors were encountered: