Skip to content

Start uninitialized Wasm exports in TDZ? #18

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.

Sign up for GitHub

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

Jump to bottom
Closed
littledan opened this issue Oct 15, 2018 · 0 comments
Closed

Start uninitialized Wasm exports in TDZ? #18

littledan opened this issue Oct 15, 2018 · 0 comments

Comments

@littledan
Copy link
Collaborator

In the README for this proposal, both before and after #13, Wasm exports are initialized as undefined, from the beginning of the evaluation phase, before the evaluation of the particular module runs. ES2015 introduces the "temporal dead zone", a mechanism where undefined things can trigger a ReferenceError rather than mysteriously show up as undefined. Would it make sense to use that here?
This was referenced Oct 16, 2018
Open
Merged
xtuc pushed a commit to xtuc/esm-integration that referenced this issue Aug 13, 2019
@littledan @xtuc
Edits for alignment with the JS API specification
6be39fc 
- Initialize Wasm exports in TDZ; closes WebAssembly#18
- Document motivation for no circular modules and circular imports
  of functions as a follow-on; closes WebAssembly#17
- Avoid use of the term "live binding"; closes WebAssembly#19
- Permit imports of Numbers as constant globals; closes WebAssembly#16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@littledan