RoaringBitmap / RoaringBitmap/roaring
HICAMP Bitmaps, any inspiration
Open
Nobody has claimed this yet.
question
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
I ran across a paper about HICAMP Bitmaps from folks at Stanford, and wondered if there were any good ideas to be learned from it.
http://web.stanford.edu/~hlitz/papers/a7-wang.pdf
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 linked HICAMP Bitmaps paper and comparing its ideas with this repository's current bitmap implementation. The issue does not name files, tests, an entry point, or a concrete change, so a maintainer would need to define the proposed work and what completion means before a newcomer can begin.
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