Tracking Issue for `core::iter::zip`

[cuviper]

Feature gate: #![feature(iter_zip)]

This is a tracking issue for core::iter::zip, a function that combines two IntoIterator arguments into a Zip iterator.

Public API

// core::iter
pub fn zip<A, B>(a: A, b: B) -> Zip<A::IntoIter, B::IntoIter>
where
    A: IntoIterator,
    B: IntoIterator,

Steps / History

• Implementation: Add function core::iter::zip #82917
• Final commenting period (FCP) Tracking Issue for core::iter::zip #83574 (comment)
• Stabilization PR Stabilize iter::zip #91881

Unresolved Questions

• None yet.

[joshtriplett]

This has been around for a while, and I haven't seen any issues reported with it. Shall we stabilize this?

@rfcbot fcp merge

[rfcbot]

Team member @joshtriplett has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Amanieu
• @BurntSushi
• @dtolnay
• @joshtriplett
• @m-ou-se
• @yaahc

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.

[scottmcm]

Ah, the reason it's worth having instead of encouraging Iterator::zip(a, b) is that it has different bounds?

[BurntSushi]

The current docs seem to indicate that this is equivalent to Iterator::zip by referencing its docs, but doesn't call out why the free function zip exists. What is the motivation of stabilizing this?

[nullp1r]

The motivation is explained in #82917.

[rfcbot]

🔔 This is now entering its final comment period, as per the review above. 🔔

[rfcbot]

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.