-
Notifications
You must be signed in to change notification settings - Fork 1k
Improve comments and change PrimitiveArray::from_trusted_len_iter
to take an ExactSizeIterator
#8564
New issue
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
Open
tobixdev
wants to merge
2
commits into
apache:main
Choose a base branch
from
tobixdev:8543-follow-up
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Improve comments and change PrimitiveArray::from_trusted_len_iter
to take an ExactSizeIterator
#8564
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is the rationale for this change? I am thinking that maybe someone who had an iterator that knew its length but did not implement
ExactSizeIterator
would have to change their codeMaybe that is ok, but the implementation doesn't even seem to use any of the methods on
ExactSizeIterator
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah we just mentioned that as a side note in the last PR. I think it has two advantages:
However, I am also happy with the old API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also think that some of the functions could make use of len instead of size_hint. If we choose to keep
ExactSizeIterator
I'll go through them.I think another cause of incompatibility is caused by users needing to call .into_iter() manually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mbrobbel Do you have any more thoughts on which iterator bound we should use?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should use
TrustedLen
, but we can't because it's nightly-only. So the next best things isExactSizeIterator
for iterators that know their exact length. However there is a note in the docs:Since this method is marked
unsafe
we require users to make sure their iterators areTrustedLen
. This means:The motivation to use
ExactSizeIterator
here (I think) is to useExactSizeIterator::len
instead ofIterator::size_hint
. This has the same "can't beNone
" requirement on the upper bound reported by the size hint.For the bound we can use
I: IntoIterator<Item = P, IntoIter: ExactSizeIterator>
.