We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
API-wise, both min() and max() should return iterators, and we should introduce the following methods:
min()
max()
begin()
end()
find()
exists()
A binary_search_tree<T>::iterator should support the following operations:
binary_search_tree<T>::iterator
Given iterator increment and decrement support, does that imply we want to mark the iterator as a bidirectional iterator? See #146
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
API-wise, both
min()
andmax()
should return iterators, and we should introduce the following methods:begin()
: returns the result ofmin()
.end()
: returns an iterator pointing to nullptrfind()
: returns an iterator pointing to the a found value. Similar toexists()
, but with an iterator return valueA
binary_search_tree<T>::iterator
should support the following operations:Given iterator increment and decrement support, does that imply we want to mark the iterator as a bidirectional iterator? See #146
The text was updated successfully, but these errors were encountered: