Phase 4 tracking issue

Open
#13 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
wasm
Domain
compilers

Research direction

Read this phase tracker and follow its outstanding issue, #12, first. The listed entry requirements show what remains: implementations in two or more Web VMs and Community Group consensus that the feature and specification are complete. Done means those requirements are met; this issue does not identify specific files or tests to start with.

Written by the indexing model from the issue text.

Description

The entry requirements for phase 4 are:

  • Two or more Web VMs have implemented the feature and pass the test suite (where applicable).
  • At least one toolchain has implemented the feature (where applicable).
  • The spec document has been fully updated in the forked repo.
  • The reference interpreter has been fully updated in the forked repo and passes the test suite.
  • The Community Group has reached consensus in support of the feature and consensus that its specification is complete.

Outstanding issues:

  • #12

Phase 3 progress was tracked in #8.

Dominant language
WebAssembly
Stars
12
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

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/extended-name-section

All issues in WebAssembly/extended-name-section

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.