Prevent conflicting opcodes

Open
#148 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
wasm
Domain
compilers

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.

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.

Dominant language
Python
Stars
1.1k
Forks
78
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/proposals

All issues in WebAssembly/proposals

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.