-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Fix #21328 #21388
Fix #21328 #21388
Conversation
This is a breaking change. To fix it you should pass the VecMap by value instead of by reference. [breaking-change]
/// The iterator's element type is `(uint, &'r V)`. | ||
/// | ||
/// # Examples | ||
/// # Example |
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.
Examples is the convention, regardless of number of exmaples.
I would suggest against ExactSizeIterator; |
Needs tests |
@gankro I fixed the issues you pointed out and added a test |
Woah a run-pass test is way overkill. Just need some basic tests in the module that make sure the iterators produce correct output (and e.g. |
@gankro Sorry for the run-pass test 😋 ... I have added it as a normal test. |
@bors: r+ b409 |
Maybe it needs a longer string? See here: #21386 |
It registered the last one |
Also I clearly nailed it on my first try. Anyone who claims otherwise is clearly a liar? |
@bors rollup |
Thanks for reviewing! |
Thanks for contributing! 🎊 |
**Breaking change**: `VecMap::into_iter` now consumes the `VecMap`. To fix it you should pass the VecMap by value instead of by reference. [breaking-change] r? @gankro
Fixes #21328
Breaking change:
VecMap::into_iter
now consumes theVecMap
. To fix it you should pass the VecMap by value instead of by reference.[breaking-change]
r? @gankro