feat: wasm64
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing waffle's existing WebAssembly support and the wasm64 requirements described in weval#22. Trace how the library represents and processes wasm targets, then determine the scope needed for wasm64 compatibility. Done means wasm64 use cases work without regressing existing wasm behavior.
Written by the indexing model from the issue text.
Description
- Dominant language
- Rust
- Stars
- 75
- Forks
- 10
- Avg merge
- 12h 43m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from bytecodealliance/waffle
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bytecodealliance/waffle#13 · 1 comment ·
All issues in bytecodealliance/waffle
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Update dusk-bls12_381 to 0.16Possibly taken @HDauven claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
`TcpListenerService` shares one `Extensions` store across all accepted connectionsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googlefonts/fontquant#43 ·