Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Clarification regarding value parameter for WebAssembly.Global etc.

Open
  • Is something wrong?
#1,660 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
wasm
Domain
documentation

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.

Description

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 TypeError
  • new WebAssembly.Global({ "value": "externref", "mutable": true}).value == undefined

and the omitted/undefined value behaves the same for table.new, table.set, table.grow.

Dominant language
WebAssembly
Stars
3.5k
Forks
539
Avg merge
10h 24m
Merged PRs (30d)
11

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/spec

All issues in WebAssembly/spec

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.