rust/library/core/src/array, branch stable

Constify Try, From, TryFrom

2025-07-21T09:49:45+00:00

constify `Index` trait and its slice impls

2025-07-15T08:27:15+00:00

simplify receivers for some array method calls

2025-07-03T14:39:27+00:00

Update version placeholders

2025-07-01T17:54:33+00:00

impl `Default` for `array::IntoIter`

2025-05-26T07:21:03+00:00

Rollup merge of #140066 - thaliaarchi:const-array-as-mut-slice, r=jhpratt

2025-05-24T19:23:47+00:00

Stabilize `<[T; N]>::as_mut_slice` as `const` This is trivial and has no design questions. Tracked in https://github.com/rust-lang/rust/issues/133333. r? libs-api

Add `#[must_use]` to Array::map

2025-05-13T03:34:53+00:00

The output of Array::map is intended to be an array of the same size, and does not modify the original in place nor is it intended for side-effects. Thus, under normal circumstances it should be consumed. See [discussion](https://internals.rust-lang.org/t/array-map-annotate-with-must-use/22813/26). Attaching to tracking issue #75243

Stabilize <[T; N]>::as_mut_slice as const

2025-04-20T09:13:34+00:00

Auto merge of #139430 - scottmcm:polymorphic-array-into-iter, r=cuviper

2025-04-11T23:21:31+00:00

Polymorphize `array::IntoIter`'s iterator impl Today we emit all the iterator methods for every different array width. That's wasteful since the actual array length never even comes into it -- the indices used are from the separate `alive: IndexRange` field, not even the `N` const param. This PR switches things so that an `array::IntoIter` stores a `PolymorphicIter<[MaybeUninit; N]>`, which we *unsize* to `PolymorphicIter<[MaybeUninit]>` and call methods on that non-`Sized` type for all the iterator methods. That also necessarily makes the layout consistent between the different lengths of arrays, because of the unsizing. Compare that to today , where different widths can't even be deduped because the offset to the indices is different for different array widths.

PR feedback

2025-04-10T04:44:59+00:00