Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Treemap: remove_range would sometimes remove too much #129

Merged
merged 1 commit into from
Jan 29, 2024
Merged

Treemap: remove_range would sometimes remove too much #129

merged 1 commit into from
Jan 29, 2024

Conversation

Dr-Emann
Copy link
Member

remove_range would remove the whole container if the first bitmap found in the range was the last bigmap touching the range, rather than just the first part of the container.

@Dr-Emann
fix(treemap): remove_range would sometimes remove too much
50b7d7f 
remove_range would remove the whole container if the first bitmap found
in the range was the last bigmap touching the range, rather than just
the first part of the container.
@Dr-Emann Dr-Emann added the bug label Jan 28, 2024
@Dr-Emann Dr-Emann requested a review from saulius January 28, 2024 09:34
@Dr-Emann Dr-Emann merged commit 2f80732 into RoaringBitmap:master Jan 29, 2024
3 of 6 checks passed
@Dr-Emann Dr-Emann deleted the treemap_remove_range_last branch January 29, 2024 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@saulius saulius Awaiting requested review from saulius

Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Dr-Emann