WebAssembly / WebAssembly/binaryen
asyncify - option to use multiple memories
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
There are a few implementation of the nascent multiple memory proposal now. Asyncify could benefit from using a dedicated memory, which would simplify the api since you wouldn't need to specify the memory offset where unwind data lives.
Contributor 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.
Research direction
Start by reviewing the existing Asyncify implementation and the nascent WebAssembly multiple memory proposal. Determine how Asyncify could use a dedicated memory and what API changes are required; done means Asyncify supports that option without requiring callers to specify the unwind-data memory offset.
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
- 30/100