-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Refactor core::iter module #56932
Refactor core::iter module #56932
Conversation
This comment has been minimized.
This comment has been minimized.
63dcfa3
to
46ec648
Compare
This comment has been minimized.
This comment has been minimized.
6ecb30d
to
5ea4df3
Compare
This comment has been minimized.
This comment has been minimized.
5ea4df3
to
3ef4a33
Compare
This comment has been minimized.
This comment has been minimized.
64dc651
to
674d5b2
Compare
This comment has been minimized.
This comment has been minimized.
674d5b2
to
33948e4
Compare
This comment has been minimized.
This comment has been minimized.
33948e4
to
6afd55b
Compare
This comment has been minimized.
This comment has been minimized.
f3f6f6d
to
a7f5ef3
Compare
This comment has been minimized.
This comment has been minimized.
a7f5ef3
to
c7105d3
Compare
fdaa15c
to
02bda7a
Compare
This is ready to merge! If @bluss isn't available to review, maybe someone else could? |
r? @Centril |
There are some other tweaks like moving @bors r+ p=1 |
📌 Commit 02bda7a has been approved by |
Thank you so much @Centril! I agree with you on |
Refactor core::iter module A while back, I refactored `core::ops` in #42523 because the module had become a giant mess and was difficult to modify. Now, I'm doing the same with the `core::iter` module. Like the `core::ops` refactor, things have been split up into multiple commits to make rebasing easier, and so that you can follow changes. Although the diffs are hard to decipher, the only actual code changes I've made in the first few commits are to modify exports and imports. I save all of the actual code refactoring, e.g. modifying what methods are called, for the end.
☀️ Test successful - checks-travis, status-appveyor |
The contents of this file have been moved in rust-lang#56932 (520e8b0) and the file should have been removed as well.
…-DPC Remove iter_private.rs The contents of this file have been moved in rust-lang#56932 (520e8b0) and the file should have been removed as well.
…-DPC Remove iter_private.rs The contents of this file have been moved in rust-lang#56932 (520e8b0) and the file should have been removed as well.
…-DPC Remove iter_private.rs The contents of this file have been moved in rust-lang#56932 (520e8b0) and the file should have been removed as well.
…-DPC Remove iter_private.rs The contents of this file have been moved in rust-lang#56932 (520e8b0) and the file should have been removed as well.
A while back, I refactored
core::ops
in #42523 because the module had become a giant mess and was difficult to modify. Now, I'm doing the same with thecore::iter
module.Like the
core::ops
refactor, things have been split up into multiple commits to make rebasing easier, and so that you can follow changes. Although the diffs are hard to decipher, the only actual code changes I've made in the first few commits are to modify exports and imports. I save all of the actual code refactoring, e.g. modifying what methods are called, for the end.