RoaringBitmap / RoaringBitmap/roaring
Create a new bitmap structure that is value-based as opposed to interface-based
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
This incomplete PR outlined potential performance gains when replacing interface/reference containers with value-based containers. The performance difference would be particularly notable for users creating many small bitmaps. This would require a new API that could be created.
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 by reading the incomplete proposal in pull request 149 and then inspect the current bitmap implementation to understand the interface- and reference-based containers it discusses. Define the scope of the proposed value-based API and determine how performance for many small bitmaps should be measured; done requires an agreed API and evidence that it improves the stated use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100