Simplify, and optimize roaring64_bitmap_remove_range_closed #592
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Only visit existing nodes, rather than every possible container in the range This makes it feasible to use `roaring64_bitmap_remove_range_closed(r, 0, UINT64_MAX)`. Before, this would have taken forever, but now, it takes proportional time to the number of containers to remove
SLieve
approved these changes
Feb 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only visit existing nodes, rather than every possible container in the range
This makes it feasible to use
roaring64_bitmap_remove_range_closed(r, 0, UINT64_MAX). Before, this would have taken forever, but now, it takes proportional time to the number of containers to remove.See #549 (the first checkbox)