-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Use len
instead of size_hint
where appropiate
#34425
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
Conversation
This makes it clearer that we're not just looking for a lower bound but rather know that the iterator is an `ExactSizeIterator`.
(rust_highfive has picked a reviewer for you, use r? to override) |
Doesn’t |
If that were the case, we should rather modify But it looks like LLVM can see right through it:
produces the same bytecode
|
⌛ Testing commit 8ff5c43 with merge ad07411... |
💔 Test failed - auto-mac-64-opt |
@bors: retry On Thu, Jun 23, 2016 at 4:00 PM, bors [email protected] wrote:
|
Use `len` instead of `size_hint` where appropiate This makes it clearer that we're not just looking for a lower bound but rather know that the iterator is an `ExactSizeIterator`.
@bors: retry force clean
|
Use `len` instead of `size_hint` where appropiate This makes it clearer that we're not just looking for a lower bound but rather know that the iterator is an `ExactSizeIterator`.
This makes it clearer that we're not just looking for a lower bound but
rather know that the iterator is an
ExactSizeIterator
.