rust-lang / rust-lang/rust

Tracking Issue for `const_array`

Open
#147,606 3 comments 14 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(const_array)]

This is a tracking issue for const [T]::map and array::from_fn.

Public API
// core::array
impl<T, const N: usize> [T; N] {
    pub const fn map<F, U>(self, f: F) -> [U; N]
    where
        F: [const] FnMut(T) -> U + [const] Destruct,
        U: [const] Destruct;
}

pub const fn from_fn<T: [const] Destruct, const N: usize, F>(f: F) -> [T; N]
where
    F: [const] FnMut(usize) -> T + [const] Destruct;

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

  • Implementation: #147071
  • Final comment period (FCP)^1
  • Stabilization PR
Unresolved Questions
  • Should array::try_map be constified

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the public API in core::array and review implementation PR #147071. Follow the feature lifecycle through the final comment period and stabilization PR, while resolving the open question about constifying array::try_map. Done means the tracking checklist reaches stabilization.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.