WebAssembly / WebAssembly/testsuite
Checking in `.bin.wast`
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 249
- Forks
- 65
- Avg merge
- 33m
- Merged PRs (30d)
- 5
Description
In maintaining https://github.com/titzer/wizard-engine, we made the decision to only parse .wast tests where the modules themselves are in binary, i.e. .bin.wast. This has been very helpful in avoiding both the work and potential incompatibilities with implementing our own parser for the entire text format. To date, Wizard's strategy has been to check out the spec repo and proposal repos, building their respective interpreters, and then generate the .bin.wast.
As it turns out, as proposals either stagnate or get their tests merged into the main spec, their respective repos get stuck with their respective toolchains (to wit, old versions of Ocaml, ocamlbuild, or dune).
I was wondering if there is any appetite for building the spec interpreter for each of the tracked proposals and then also building the .bin.wast outputs of them, and checking them in here automatically as part of the CI.
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 reviewing how the spec repo and proposal repositories are currently checked out, built, and used to generate .bin.wast files. The work is done when CI can build the interpreter and generate checked-in .bin.wast outputs for each tracked proposal without depending on obsolete local toolchains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100