WebAssembly / WebAssembly/spec
UINT32_MAX as various index values
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 3.5k
- Forks
- 539
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 13
Description
certain wasm runtimes creatively misuse UINT32_MAX to represent alternatives, for example in exception handling implementations to differentiate catch from catch_all.
it'd perhaps be a good idea to make sure such modules are treated as invalid instead.
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
The issue names no files, tests, or entry points. Start by reviewing the WebAssembly validation rules for index values and exception handling, especially the distinction between catch and catch_all; establish the expected invalid-module behavior for UINT32_MAX and cover it in the relevant specification tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100