Skip to content

Tracking Issue for core::iter::chain #125964

Description

@rossmacarthur

Feature gate: #![feature(iter_chain)]

This is a tracking issue for the core::iter::chain function that combines two IntoIterator arguments together into a Chain iterator.

Public API

// core::iter
pub fn chain<A, B>(a: A, b: B) -> Chain<A::IntoIter, B::IntoIter>
where
    A: IntoIterator,
    B: IntoIterator<Item = A::Item>;

Steps / History

Unresolved Questions

  • None yet.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    T-libs-api[DEPRECATED; DO NOT USE]
    on Jun 4, 2024
  2. scottmcm commented on Sep 23, 2024

    @scottmcm
    Member

    I was reminded of this by it showing up on URLO: https://users.rust-lang.org/t/iterator-extension-allthesame/117972/3?u=scottmcm

    Can we just stabilize it? Having both sides be IntoIterator is nice.

    Only other choice I could come up with for the signature would be

    pub fn chain<A, B>(a: impl IntoIterator<IntoIter = A>, b: impl IntoIterator<IntoIter = B>) -> Chain<A, B>
    where
        A: Iterator,
        B: Iterator<Item = A::Item>;

    but that really doesn't seem materially better, so as it is seems good.

  3. japm48 commented on Dec 23, 2024

    @japm48
    Contributor

    Hi, any news on this?
    I'm unfamiliar with the process, but is there any reason why the FCP has not yet started?

  4. rossmacarthur commented on Dec 24, 2024

    @rossmacarthur
    ContributorAuthor

    @rust-lang/libs-api can we start an FCP for this?

  5. rossmacarthur commented on Jul 16, 2025

    @rossmacarthur
    ContributorAuthor

    @Mark-Simulacrum / @workingjubilee / @jhpratt can we start an FCP for this?

  6. jhpratt commented on Jul 16, 2025

    @jhpratt
    Member

    Unsure why I'm being pinged; I have nothing to do with FCPs, nor have I ever. Maybe try asking on Zulip?

  7. Amanieu commented on Jul 22, 2025

    @Amanieu
    Member

    @rfcbot merge

  8. rfcbot commented on Jul 22, 2025

    @rfcbot

    Team member @Amanieu 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.

  9. added
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.
    on Jul 22, 2025
  10. added
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    and removed
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    on Aug 5, 2025
  11. rfcbot commented on Aug 5, 2025

    @rfcbot

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

  12. added
    to-announceAnnounce this issue on triage meeting
    and removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on Aug 15, 2025
  13. rfcbot commented on Aug 15, 2025

    @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.

  14. added a commit that references this issue on Aug 15, 2025
    2776a21
  15. added a commit that references this issue on Aug 16, 2025
    3fa0814
  16. added a commit that references this issue on Aug 18, 2025
    2567930
  17. added this to the 1.91.0 milestone on Sep 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-api[DEPRECATED; DO NOT USE]disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions