WebAssembly / WebAssembly/binaryen
`Module.readBinary` use current spec as default feature set.
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
Currently, the Module.readBinary function uses mvp as the default feature set. I think it may make more sense to use a feature set equivalent to the current wasm spec. Currently wasm v3.0 has features like tail calls and gc enabled by default. My reasoning for this is that, over time as we get more and more wasm proposals, readBinary seems like its going to become less and less useful otherwise.
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 locating the Module.readBinary entry point and checking how its default feature set is selected. Compare that default with the current WebAssembly specification, including the issue's mention of tail calls and GC. Done means readBinary uses a feature set equivalent to the current spec rather than mvp, with tests covering the changed defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100