RoaringBitmap / RoaringBitmap/roaring
Support and / or workarounds for using 32 bytes / 256 bits numbers?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
Hi there, I am wondering if there is a support for 32 bytes / 256 bits numbers (be it bigint-like, or byte / uint32 array) with roaring bitmaps, can't find any info, not sure whether this is actually achievable.
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 files, tests, or entry points. Start by reviewing the existing roaring bitmap API and documentation for integer-width assumptions, then establish whether 32-byte or 256-bit values are supported or require a workaround and define a concrete acceptance criterion.
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
- 25/100