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

Minor errors in 3.0 binary format

Open
  • Is something wrong?
#2,041 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
wasm
Domain
documentation

Research direction

Read the 3.0 binary values and modules sections linked in the issue, comparing each with the corresponding 2.0 definitions. Verify the recursive sN production and the relationship between typeid and code section arities; done means the specification reflects the intended definitions and the wording is unambiguous.

Written by the indexing model from the issue text.

Description

  1. The third (recursive) case of the binary definition of sN should have i:s instead of i:u
  1. (arguable?) The module binary definition uses * everywhere for all the section lists, but the typeid and code sections should have a distinguished arity to make in unambiguous that they must have the same number of entries as each other (while other sections are allowed to have different sizes) - 2.0 used n.

These were found while hand-mechanising part of the binary format in Isabelle.

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.