WebAssembly / WebAssembly/wasi-libc
Investigate mimalloc
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1k
- Forks
- 251
- Avg merge
- 7h 15m
- Merged PRs (30d)
- 3
Description
It'd be nice to provide alternative malloc implementations, with different code size vs performance tradeoffs.
See the comment here about mimalloc.
Contributor guide
No contributing guide indexed for this repository
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 with the linked comment on pull request 89 and inspect how wasi-libc currently provides malloc implementations. Define the supported alternative allocator scope and the code-size versus performance criteria; the work is done when those tradeoffs and an implementation path are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, wasm
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100