-
Notifications
You must be signed in to change notification settings - Fork 43
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
Bindings CRoaring 3.0, including 64 bit bitmaps #125
Conversation
Man I love differential fuzzing. Finding some issues in roaring64, and our treemap: #126, RoaringBitmap/CRoaring#552, RoaringBitmap/CRoaring#550, RoaringBitmap/CRoaring#551 |
c9867b4
to
dea654b
Compare
1a05364
to
d7cf56c
Compare
e2dd6a8
to
b112e7e
Compare
97b75be
to
8779205
Compare
Don't remove run compression for treemap since we don't support it in roaring64 yet
@saulius Believe this is ready 🎉 |
Woha, this is fascinating @Dr-Emann, great work! |
/// assert_eq!(first_over_50, ControlFlow::Break(100)); | ||
/// ``` | ||
#[inline] | ||
pub fn for_each<F, O>(&self, f: F) -> ControlFlow<O> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice use of ControlFlow
, very elegant!
Looks great! Given this introduces changes to |
the fuzz_ops64 target includes deserializing, and performing actions on the bitmap too
croaring-sys definitely requires a major version bump, but croaring-rs shouldn't have any breaking changes, and cargo-semver-checks agrees
I believe we don't actually need a major version bump, I don't think there's any breaking changes (and That said, I'm not against a 2.0, especially since croaring just did a major version bump. |
See CRoaring 3.0.0 release