microsoft / microsoft/mimalloc
ABI stability and SONAME version
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
@thomcc said in https://github.com/purpleprotocol/mimalloc_rust/issues/73#issuecomment-968130952: “mimalloc isn't fully ABI stable”. Is this statement (still) true? If so, can you please focus more on ABI stability and always bump SONAME when ABI is changed in a backward incompatible way? This is important for packaging in Linux distributions.
/cc @daanx
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
No files or tests are named. Start by reviewing the project's current ABI and SONAME versioning behavior, then determine how backward-incompatible public C ABI changes are identified and released. Done means the ABI stability status is established and incompatible changes consistently receive an appropriate SONAME bump for Linux packaging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100