Pure Rust implementation of mimalloc
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- operating-systems
Research direction
Start by reading the mimalloc codebase and the issue's proposed Rust port context. The payload does not name files or tests; a concrete public repository or draft PR with CI for C test equivalence would define the implementation scope and what done looks like.
Written by the indexing model from the issue text.
Description
Hello mimalloc team and community,
First of all, thank you for creating and maintaining such a robust and well-designed allocator. It's an incredibly valuable piece of technology.
We’ve developed an LLM-powered C-to-Rust transpiler that goes far beyond mechanical translation (e.g., C2Rust).
We’ve already run our end-to-end pipeline on the full mimalloc codebase and are currently in active testing.
Early Metrics vs. C2Rust (on mimalloc core):
| Tool | RP decl | RP deref | RP arithmetic | Unsafe Line |
|---|---|---|---|---|
| Our tool | 44 | 41 | 38 | 51 |
| c2rust | 478 | 1274 | 477 | 9903 |
RP = Raw Pointer
Key advantages of our tool output:
- Minimal unsafe: Only in well-encapsulated, reviewed modules (e.g., intrusive lists)
We’d love your feedback:
-
Are you open to reviewing a preview of the generated mimalloc port?
(We can share a public repo or draft PR with CI running C test equivalence.) -
Initial thoughts on LLM-assisted transpilation for allocator code?
-
Would a PR be welcome at this stage?
Even as an experimental, parallel implementation (e.g.,mimalloc-rs), not to replace C, but to explore the design space.
Looking forward to your thoughts, happy to hop on a call or share early artifacts.
Thanks again for the thoughtful discussion and for building such a solid foundation in mimalloc
Thanks
Saman
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 1.2k
- Avg merge
- 18h 12m
- Merged PRs (30d)
- 20
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 microsoft/mimalloc
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Building mimalloc with `-Wundef` compiler flag logs many warnings on undefined macrosPossibly taken @vstinner claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/mimalloc#1506 · 5 comments ·
Maintainers usually reply within 1 day
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/mimalloc#1113 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/mimalloc#886 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/mimalloc#368 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/mimalloc
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
389ds/389-ds-base#8157 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
coolsnowwolf/lede#14305 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days