Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upBoundNames of default exports #603
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
allenwb
Jun 7, 2016
Member
It's there so that the early error checks in 15.2.1.1 that use LexicallyDeclaredNames work across all export default declarations.
However, it appears that the first two rules (when applied to export default declarations) may be redundant with rule 3 (see the note that follow the rules). If that is the case that it may be valid to eliminate the unconditional inclusion of "default" as a BoundName.
This probably needs a more careful analysis.
|
It's there so that the early error checks in 15.2.1.1 that use LexicallyDeclaredNames work across all However, it appears that the first two rules (when applied to This probably needs a more careful analysis. |
GeorgNeis commentedJun 7, 2016
15.2.3.2 Static Semantics: BoundNames always includes "default" for a default export, even if there already is a local name for it. For instance:
I couldn't find a justification for that, am I missing something?