rust/library/core/src/array/mod.rs, 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

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

Promise `array::from_fn` in generated in order of increasing indices

2025-03-29T08:06:43+00:00

Rollup merge of #135489 - RalfJung:TryFromSliceError, r=tgross35

2025-01-24T07:08:06+00:00

remove pointless allowed_through_unstable_modules on TryFromSliceError This got added in https://github.com/rust-lang/rust/pull/132482 but the PR does not explain why. `@lukas-code` do you still remember? Also Cc `@Noratrieb` as reviewer of that PR. If I understand the issue description correctly, all paths under which this type is exported are stable now: `core::array::TryFromSliceError` and `std::array::TryFromSliceError`. If that is the case, we shouldn't have the attribute; it's a terrible hack that should only be used when needed to maintain backward compatibility. Getting some historic information right is IMO *not* sufficient justification to risk accidentally exposing this type via more unstable paths today or in the future.

core: add `#![warn(unreachable_pub)]`

2025-01-20T17:35:32+00:00