Skip to content

Tracking Issue for const_array_each_ref #133289

Closed

Description

@bjoernager

Feature gate: #![feature(const_array_each_ref)]

This is a tracking issue for supporting the each_ref and each_mut methods in [T; N] in constant expressions.

Public API

impl<T, const N: usize> [T; N] {
    pub const fn each_ref(&self) -> [&T; N];

    pub const fn each_mut(&mut self) -> [&mut T; N];
}

Unresolved Questions

  • None yet.

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 Nov 21, 2024
  2. added a commit that references this issue on Nov 22, 2024
  3. added a commit that references this issue on Nov 22, 2024
  4. RalfJung commented on Jul 3, 2025

    @RalfJung
    Member

    @rust-lang/libs-api @rust-lang/wg-const-eval I see no blocker for const-stabilizing these functions, which have been stable since Rust 1.77. The implementation had to be changed to use a while loop instead of an iterator, but we can always change it back later when const traits become more capable.

  5. rfcbot commented on Jul 4, 2025

    @rfcbot

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

  6. 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 4, 2025
  7. fee1-dead commented on Aug 9, 2025

    @fee1-dead
    Member

    hi @BurntSushi, @joshtriplett, @m-ou-se: waiting for checked boxes :)

  8. 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 10, 2025
  9. rfcbot commented on Aug 10, 2025

    @rfcbot

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

  10. bjoernager commented on Aug 10, 2025

    @bjoernager
    ContributorAuthor

    Stabilisation PR: #145211 #143383

  11. 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 20, 2025
  12. rfcbot commented on Aug 20, 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.

  13. added 5 commits that reference this issue on Aug 20, 2025
  14. added a commit that references this issue on Aug 21, 2025
  15. added a commit that references this issue on Aug 26, 2025
  16. 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