You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several parts of the specification that make use of cover grammars, but the details can be buried. The most obvious example is at Left-Hand-Side Expressions, where there is a CallExpression[Yield, Await] : CoverCallExpressionAndAsyncArrowHead[?Yield, ?Await] production but no indication of the supplemental CallMemberExpression[Yield, Await] : MemberExpression[?Yield, ?Await]Arguments[?Yield, ?Await] refining its CoverCallExpressionAndAsyncArrowHead that appears after a lot of intervening productions.
I can think of a few ways to address this, and they're non-exclusive:
Promote "Supplemental Syntax" into actual subsections so they appear in the table of contents.
Annotate productions to indicate that they are subject to refinement (may require changing grammarkdown).
Give each cover grammar goal symbol a dedicated subsection that references its refinements, such that e.g. clicking on |CoverCallExpressionAndAsyncArrowHead| in the |CallExpression| productions goes to a section that explains its use in both |CallExpression| (with a link to |CallMemberExpression|) and |AsyncArrowFunction| (with a link to |AsyncArrowHead|).
The text was updated successfully, but these errors were encountered:
There are several parts of the specification that make use of cover grammars, but the details can be buried. The most obvious example is at Left-Hand-Side Expressions, where there is a CallExpression[Yield, Await] : CoverCallExpressionAndAsyncArrowHead[?Yield, ?Await] production but no indication of the supplemental CallMemberExpression[Yield, Await] : MemberExpression[?Yield, ?Await] Arguments[?Yield, ?Await] refining its CoverCallExpressionAndAsyncArrowHead that appears after a lot of intervening productions.
I can think of a few ways to address this, and they're non-exclusive:
The text was updated successfully, but these errors were encountered: