RoaringBitmap / RoaringBitmap/roaring
Create low-allocation immutable Roaring bitmaps
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
Some users have a many bitmaps on disk. Loading them up temporarily for operations is expensive due in part to the allocation of new instances in this process...
newrb:= roaring.New()
newrb.ReadFrom(buf)
Related PR https://github.com/RoaringBitmap/roaring/pull/263
Also related to issue https://github.com/RoaringBitmap/roaring/issues/193
cc @guymolinari @jacksonrnewhouse
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 Go example using roaring.New and ReadFrom, then review related PR #263 and issue #193 for prior context. Define the immutable bitmap loading and operation requirements, and confirm that the resulting approach avoids unnecessary instance allocation for on-disk bitmaps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100