You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
When last element was swapped with the removed element it was only propagated downwards.
Depending if the swapped value is greater or smaller than its parent it may instead
need to propagate upwards.
FixesARMmbed#108
Change-Id: I9583a3412ccb88166d4e3091ed31a4c8a3aa4486
When last element was swapped with the removed element it was only propagated downwards.
Depending if the swapped value is greater or smaller than its parent it may instead
need to propagate upwards.
FixesARMmbed#108
Change-Id: I9583a3412ccb88166d4e3091ed31a4c8a3aa4486
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The BinaryHeap consistency can break if an item is removed under specific conditions. The bug can be reproduced with the code below:
The above code should print out all the values in rising order, i.e. the expected output is:
However, the actual output is:
It looks like the algorithm in
remove()
is not correctThe text was updated successfully, but these errors were encountered: