Priority list for OptimizeInstructions reviews

Open
#4,277 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
18/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
wasm
Domain
compilers

Research direction

Start with the linked discussion in PR #4265 and inspect the listed PRs #4272, #4307, #4282, #4145, #4291, #4266, and #4249. Done means the priority list is maintained and older OptimizeInstructions PRs have been reviewed or updated, but the issue does not define a specific update or acceptance criteria.

Written by the indexing model from the issue text.

Description

@kripken suggested creating a list of PRs here, sorted in order of priority (the most important first):

  • #4272
  • #4307
  • #4282
  • #4145
  • #4291
  • #4266
  • #4249

I think that's enough for now. I then plan to review and update older PRs

Dominant language
WebAssembly
Stars
8.6k
Forks
885
Avg merge
2d 1h
Merged PRs (30d)
70

Contributor guide

Open the contributing guide

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/binaryen

All issues in WebAssembly/binaryen

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.