Tracking Issue for `Option::zip` and `Option::zip_with` (feature `option_zip`) · Issue #70086 · rust-lang/rust

- [GitHub Copilot
  
  Write better code with AI](https://github.com/features/copilot)
[GitHub Advanced Security

Find and fix vulnerabilities](https://github.com/security/advanced-security)
[Actions

Automate any workflow](https://github.com/features/actions)
[Codespaces

Instant dev environments](https://github.com/features/codespaces)
[Issues

Plan and track work](https://github.com/features/issues)
[Code Review

Manage code changes](https://github.com/features/code-review)
[Discussions

Collaborate outside of code](https://github.com/features/discussions)
[Code Search

Find more, search less](https://github.com/features/code-search)
Explore
Learning Pathways
Events & Webinars
Ebooks & Whitepapers
Customer Stories
Partners
Executive Insights
- [GitHub Sponsors
  
  Fund open source developers](https://github.com/sponsors)
[The ReadME Project

GitHub community articles](https://github.com/readme)
- [Enterprise platform
  
  AI-powered developer platform](https://github.com/enterprise)
Pricing

Use saved searches to filter your results more quickly

This is a tracking issue for #![feature(option_zip)] which was introduced in #69997.

Tracking issues are used to record the overall progress of implementation.

They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.

A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.

Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Should we also include zip_with in the public API? Seems like a niche API and is easily replaced with a.zip(b).map(f).