WebAssembly / WebAssembly/proposals
Prevent conflicting opcodes
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
In https://github.com/WebAssembly/exception-handling/issues/145, it was pointed out that exception-handling and function-references were both using 0x16. Perhaps a central list of proposed opcodes would help prevent that in the future.
Contributor guide
No contributing guide indexed for this repository
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 the linked exception-handling issue 145 and the proposals repository's existing process for tracking opcode assignments. Determine whether a central list is in scope and what information it would need; done requires an agreed approach that prevents conflicting proposed opcodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100