Tracking Issue for `Vec::as_non_null()`

Feature gate: #![feature(vec_as_non_null)]

This is a tracking issue for Vec::as_non_null()

See also #157345 for a similar feature.

Public API

impl<T, A: Allocator> Vec<T, A> {
    pub const fn as_non_null(&mut self) -> NonNull<T> { .... }
}

Steps / History

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

• ACP: https://github.com/rust-lang/libs-team/issues/440
• Implementation:
  • https://github.com/rust-lang/rust/pull/130624
    • The above implementation added the method to the box_vec_non_null feature, at the tracking issue https://github.com/rust-lang/rust/issues/130364
  • This method has #[rustc_as_ptr] added to it, and is split out of the box_vec_non_null feature into its own feature (this tracking issue): https://github.com/rust-lang/rust/pull/157226
• Final comment period (FCP)^1
• Stabilization PR

Unresolved Questions

• Confirm whether we want a &self or &mut self argument.
  • See previous discussion at #t-opsem > Should `slice/Vec::as_non_null`take `&self` or `&mut self`? and Libs-API Meeting 2026-06-09

Start with the public API and the linked implementation PRs #130624 and #157226, then read the Zulip discussion and Libs-API meeting notes about the receiver choice. Done means resolving whether the method takes &self or &mut self, completing the final comment period, and opening the stabilization PR.