WebAssembly / WebAssembly/spec
Clarification regarding value parameter for WebAssembly.Global etc.
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 3.5k
- Forks
- 539
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 13
Description
Please confirm if the intended behavior for reference-typed WebAssembly.Global is the following:
new WebAssembly.Global({ "value": "anyfunc", "mutable": true}).value == nullnew 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 for table.new, table.set, table.grow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the WebAssembly.Global cases for anyfunc and externref, then examine the omitted and undefined value behavior requested for table.new, table.set, and table.grow. Done means the intended semantics are resolved and clearly recorded in the WebAssembly specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100