RoaringBitmap / RoaringBitmap/croaring-rs
Could we get the memory size of Treemap that occupies
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 174
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
As title described
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
The issue names no file, test, or entry point. Start by locating the Treemap API in the Rust FFI wrapper and its underlying CRoaring implementation, then determine which memory-size metric should be exposed; done when callers can obtain a tested occupied-size value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100