-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Bounded Iterator #5
Labels
Milestone
Comments
5 tasks
This was referenced Sep 22, 2021
8 tasks
Kerollmops
pushed a commit
that referenced
this issue
Oct 18, 2021
not-jan
pushed a commit
to not-jan/roaring-rs
that referenced
this issue
Aug 31, 2022
…ove_range} and Treemap::remove_range to accept `RangeBounds`; Fix boundary issue;
not-jan
pushed a commit
to not-jan/roaring-rs
that referenced
this issue
Aug 31, 2022
92: Rework the insert/remove_range functions with RangeBounds r=Kerollmops a=Kerollmops This PR fixes RoaringBitmap#5 by reworking the `Bitmap::insert_range` and `Bitmap::remove_range` functions to accept any type that implement [the `RangeBounds` trait](https://doc.rust-lang.org/nightly/core/ops/trait.RangeBounds.html). Note that it is a breaking change and therefore involves bumping the crate version carefully. The current version of all these functions was accepting an [exclusive `Range<u64>`](https://doc.rust-lang.org/nightly/core/ops/struct.Range.html) to let user define all possible integers in the range `0` to `u32::MAX`, but as it is an exclusive range, a `u64` was required. `@josephglanville,` could you please take a look at this PR? When you got time 😃 Co-authored-by: Clément Renault <[email protected]> Co-authored-by: oliverdding <[email protected]> Co-authored-by: Kerollmops <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Waiting on
Bound
to be merged with rust-lang/rust#20082.§ describing bounded iterators in the RFC
The text was updated successfully, but these errors were encountered: