RoaringBitmap / RoaringBitmap/roaring
Feature request for 128bit for ipv6 usage.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
@lemire i would like to use 128bit for ipv6, thought of having 2 roaring bitmaps of 64bit each and splitting the ipv6 into 2 segments but i realised i have to call the roaring bitmap from 2 memory location twice.
- possible to make a 128bit version?
- do u have suggestions to make this faster or better? is it advisable to use ipv6 detection for "flagging" it as a banned ip or similar?
specifically asked u coz i know u are expert in extreme optimization and thanks for all the write ups you have done etc.
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
No files, tests, or entry points are named. Start by reviewing the repository's existing 64-bit roaring bitmap API and how values are represented, then determine the requirements and performance tradeoffs for 128-bit IPv6 support; done requires an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100