Add fast last(), last_mut() and upper_bound() operations… #12
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.
…via additional constraints on internal vec
I wrote this as a proof of concept to satisfy a use-case of mine (actually, in my use case elements are never removed so the implementation could be simpler).
This adds three new operations which should all be constant time, at the cost of potentially making
remove()
andsplit_off()
O(n)
operations. Thoughts?The new operations could of course be added without the other changes, but in that case they would merely be convenience wrappers.