Tracking Issue for const_intoiterator_identity · Issue #90603 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

Feature gate: #![feature(const_intoiterator_identity)]

This is a tracking issue for the const IntoIterator implementation for types that are already iterators.

This is not a new api; only constifying an existing one

Public API

// core::iter // actually core/iter/traits/collect.rs, but re-exported from there. impl<I: ~const Iterator> const IntoIterator for I { type Item = I::Item; type IntoIter = I; fn into_iter(self) -> I; }

Steps / History

• Implementation: Unstably constify impl<I: Iterator> IntoIterator for I #90602
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• Should it bound on the resultant Iterator being a const Iterator or not? I've gone with having the bound for now. Note: This can be relaxed later without breaking any code.