WebAssembly / WebAssembly/wabt
Add a flag that constrains features to the W3C recommendation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.1k
- Forks
- 827
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 18
Description
Since this is a repo in the org for the W3C core recommendation, I think it is a fair ask to have a flag that constrains features to what's included in that, and no more. It will help with tracking https://github.com/WebAssembly/wabt#supported-proposals and make upgrades seamless.
I'm not asking for this to be by default turned on, rather to make it possible to achieve undoing all the flags that turn on things not in the recommended spec. Ex. --enable-1.0 (please don't call whatever flag MVP as that's jargon and not a W3C version number).
Ex. just like enable-all
--enable-1.0 Enable only features in version 1.0 of the core WebAssembly standard
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 does not name implementation files or tests. Start by tracing the existing enable-all and --enable-1.0 command-line option handling, then inspect how supported WebAssembly proposals are represented. Done means a flag can enable exactly the features in the W3C core WebAssembly 1.0 recommendation without changing the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100