Tracking Issue for `const_array_each_ref`

[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];
}

• Implementation: Support each_ref and each_mut in [T; N] in constant expressions. #133288
• Final comment period (FCP)
• Stabilization PR: stabilize const_array_each_ref #143383

Unresolved Questions

• None yet.

[RalfJung]

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

[dtolnay]

@rfcbot fcp merge

const for these 2 stable functions:

• https://doc.rust-lang.org/nightly/std/primitive.array.html#method.each_ref
• https://doc.rust-lang.org/nightly/std/primitive.array.html#method.each_mut

[rfcbot]

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

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.

[fee1-dead]

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

[rfcbot]

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