-
Notifications
You must be signed in to change notification settings - Fork 436
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
Clarification regarding value parameter for WebAssembly.Global etc. #1660
Comments
That is my understanding of WebAssembly.Global behavior. It's implied by the behavior of DefaultValue [1]. The Table JS-API methods also have this behavior as well. [1] https://webassembly.github.io/spec/js-api/index.html#defaultvalue |
Hmm, as far as I can tell from https://webidl.spec.whatwg.org/#create-an-interface-object , the first two should be equivalent (ORA returns |
Might be further fallout from engines not actually using Web IDL? |
Please confirm if the intended behavior for reference-typed WebAssembly.Global is the following:
new WebAssembly.Global({ "value": "anyfunc", "mutable": true}).value == null
new WebAssembly.Global({ "value": "anyfunc", "mutable": true}, undefined)
throws TypeErrornew WebAssembly.Global({ "value": "externref", "mutable": true}).value == undefined
and the omitted/
undefined
value behaves the same fortable.new
,table.set
,table.grow
.The text was updated successfully, but these errors were encountered: