Methods named len
, is_empty
and capacity
should take constant time
#288
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.
Today, I wanted to switch to using
Vec::with_capacity
instead ofVec::new
while iterating over atoml_edit::Table
:But to my surprise, the
Table::len
method actually takes O(n) time, as it is implemented withIterator::count
:This is surprising and can make people's code slower, without them realizing why. Library authors should choose different names for a
len
method if it doesn't take constant time, such ascount
.I found a discussion about this from 2017, and decided to open a PR to add this guideline