Tracking Issue for const_nonnull_new

[lilasta]

Feature gate: #![feature(const_nonnull_new)]

This is a tracking issue for implementing NonNull::new.

Public API

// core::ptr
impl<T: ?Sized> NonNull<T> {
    pub const fn new(ptr: *mut T) -> Option<Self>;
}

Steps / History

• Implementation: Make NonNull::new const #93236
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• Quasi-blocked on Tracking issue for const <*const T>::is_null #74939

[workingjubilee]

Quasi-blocked on #93235

[RalfJung]

Quasi-blocked on #93235

I assume you mean #74939.

That one just finished FCP, so we can now move ahead with NonNull::new. :)
@rust-lang/libs-api this should be, finally, ready to be stabilized.

[dtolnay]

@rfcbot fcp merge

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

[RalfJung]

@BurntSushi @joshtriplett @m-ou-se friendly FCP checkbox reminder :) There's tons of cases out there of people using the unsafe NonNull::new_unchecked just because it works in const, so making its safe cousin available would be nice.

[rfcbot]

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

[rfcbot]

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

This will be merged soon.