Tracking Issue for const fn <*T>::is_null

[oli-obk]

This is a tracking issue for making the is_null method on raw pointers const fn
The feature gate for the issue is #![feature(const_ptr_is_null)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

• Implement
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

[RalfJung]

Cc @rust-lang/wg-const-eval

[RalfJung]

Isn't this blocked on #53020 ? Right now, (&0 as *const _).is_null() will error even with Miri unleashed (and that is good, ptr comparison is a complicated subject).

[oli-obk]

yeaaa... I was a bit overexcited about this one. As my implementation quickly exploded to exactly what you're saying there. I'll close this issue again, there's no point in tracking it here. I'll just add it to the skill tree