RoaringBitmap / RoaringBitmap/roaring-rs
No way to do non-inplace operations without operators
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 957
- Forks
- 119
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 1
Description
let rb1 = RoaringBitmap::from_iter(0..1u32);
let rb2 = RoaringBitmap::from_iter(2..3u32);
let rb3 = &rb1 | &rb2;
No way to do the above using an inherent method on rb1, might be worth adding something like let rb3 = rb1.or_into_a_new_bitmap(rb2); (and for the other operators).
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 reviewing RoaringBitmap's current operator support and the non-inplace operation shown in the issue. Define the inherent-method API for the other operators, then ensure each operation returns a new bitmap without requiring operator syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100