New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Superfluous check in [[Get]] for Module Namespace Exotic Object? #602

Closed
GeorgNeis opened this Issue Jun 7, 2016 · 1 comment

Comments

Projects
None yet
3 participants
@GeorgNeis
Contributor

GeorgNeis commented Jun 7, 2016

In 9.4.6.8, step 11 throws an exception if the module's environment is undefined. How can this ever happen? The environment is set in 15.2.1.16.4 ModuleDeclarationInstantiation and never unset as far as I can tell. I don't see how a namespace object's [[Get]] can be invoked without ModuleDeclarationInstantiation having happened before.

@allenwb

This comment has been minimized.

Show comment
Hide comment
@allenwb

allenwb Jun 7, 2016

Member

The spec. allows an implementation to extend the language with additional kinds of modules. 15.2.1.16.4 only applies to Source Text Modules. 9.4.6.8 must work will all kinds of modules, including implementation provided kinds. Step 11 is there just in case the environment of such an extension module has not been set.

Member

allenwb commented Jun 7, 2016

The spec. allows an implementation to extend the language with additional kinds of modules. 15.2.1.16.4 only applies to Source Text Modules. 9.4.6.8 must work will all kinds of modules, including implementation provided kinds. Step 11 is there just in case the environment of such an extension module has not been set.

@bterlson bterlson closed this Jun 8, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment