Tracking Issue for const_exposed_provenance

[RalfJung]

Feature gate: #![feature(const_exposed_provenance)]

This is a tracking issue for calling with_exposed_provenance in const fn.

Public API

// core::ptr
pub const fn with_exposed_provenance<T>(addr: usize) -> *const T;
pub const fn with_exposed_provenance_mut<T>(addr: usize) -> *mut T;

Steps / History

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

• Implementation: constify with_exposed_provenance #144539
• Final comment period (FCP)¹
• Stabilization PR: Stabilize const_exposed_provenance feature #145462

Unresolved Questions

• None yet.

Cc @rust-lang/wg-const-eval

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[clarfonthey]

You accidentally linked to this issue as the implementation instead of the PR.

[RalfJung]

@rust-lang/libs-api this has just landed in nightly, but given that int-to-ptr casts have been allowed in const fn since forever (for better or worse) and we document this as equivalent, there seems to be no reason to wait with stabilizing this.

[Amanieu]

This seems fairly straightforward.

@rfcbot merge

[rfcbot]

Team member @Amanieu 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.