WebAssembly / WebAssembly/spec
[js-api] Allow passing non-bigint values to I64 parameters
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 3.5k
- Forks
- 539
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 13
Description
This was originally discussed in https://github.com/WebAssembly/JS-BigInt-integration/issues/12.
I would like to propose revisiting but since that repo has been archived I'm restarting the conversation here.
I've worked on getting memory64 working in emscripten for that last year or so I've run into this issue many times now. The most recent and painful instance being https://github.com/emscripten-core/emscripten/issues/17969. Fixing this one is going to take a lot of effort and I think will have runtime overhead as well as add code complexity.
https://github.com/WebAssembly/design/issues/1399 also seems related.
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
Start by reading the linked JS-BigInt integration, Emscripten, and WebAssembly design discussions to understand the proposed I64 argument behavior. Then locate the relevant JavaScript API specification and reference-interpreter tests. Done means the coercion rules are agreed, specified, and covered by the repository's test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100