Add a splay tree implementation to libstd #6360
Closed
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.
I was curious if something like this was possible, and it indeed is!
I didn't want to duplicate a lot of functionality between splay trees and the existing
treemap
module, so I extracted out a lot of the iterators and implementations into theiterator
module.If this doesn't belong in libstd, it was mostly a proof-of-concept idea anyway. I remember talk about moving the current
std
away from this repo and into their own repos, so this may just belong elsewhere.Benchmark-wise, it performs about as well as expected. It's real bad on random input (when compared to
TreeMap
), and it's better on sequential input thanTreeMap
most of the time. Although that's not quite representative because splay trees are meant to be used on inputs with mild patterns anyway.Method naming would love to have #5898 as well...