-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Tracking Issue for core::iter::zip
#83574
Comments
This has been around for a while, and I haven't seen any issues reported with it. Shall we stabilize this? @rfcbot fcp merge |
Team member @joshtriplett has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
Ah, the reason it's worth having instead of encouraging |
The current docs seem to indicate that this is equivalent to |
The motivation is explained in #82917. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
… r=scottmcm Stabilize `iter::zip` Hello all! As the tracking issue (rust-lang#83574) for `iter::zip` completed the final commenting period without any concerns being raised, I hereby submit this stabilization PR on the issue. As the pull request that introduced the feature (rust-lang#82917) states, the `iter::zip` function is a shorter way to zip two iterators. As it's generally a quality-of-life/ergonomic improvement, it has been integrated into the codebase without any trouble, and has been used in many places across the rust compiler and standard library since March without any issues. For more details, I would refer to `@cuviper's` original PR, or the [function's documentation](https://doc.rust-lang.org/std/iter/fn.zip.html).
… r=scottmcm Stabilize `iter::zip` Hello all! As the tracking issue (rust-lang#83574) for `iter::zip` completed the final commenting period without any concerns being raised, I hereby submit this stabilization PR on the issue. As the pull request that introduced the feature (rust-lang#82917) states, the `iter::zip` function is a shorter way to zip two iterators. As it's generally a quality-of-life/ergonomic improvement, it has been integrated into the codebase without any trouble, and has been used in many places across the rust compiler and standard library since March without any issues. For more details, I would refer to `@cuviper's` original PR, or the [function's documentation](https://doc.rust-lang.org/std/iter/fn.zip.html).
I realize that this has already merged, but it might have been nicer as a for (((a, b), c), d) in ia.zip(ib).zip(ic).zip(id) {
// ...
}
for (a, b, c, d) in iter::zip!(ia, ib, ic, id) {
// ...
} |
@ibraheemdev that's available in https://docs.rs/itertools/latest/itertools/macro.izip.html if you'd like. It's not clear whether |
The issue is now stable: rust-lang/rust#83574
Feature gate:
#![feature(iter_zip)]
This is a tracking issue for
core::iter::zip
, a function that combines twoIntoIterator
arguments into aZip
iterator.Public API
Steps / History
core::iter::zip
#83574 (comment)iter::zip
#91881Unresolved Questions
The text was updated successfully, but these errors were encountered: