Tracking Issue for const_transmute_copy

[usbalbin]

Feature gate: #![feature(const_transmute_copy)]

This is a tracking issue for making the function mem::transmute_copy const fn.

Public API

mod mem {
    pub const unsafe fn transmute_copy<T, U>(src: &T) -> U;
}

Steps / History

• Implementation: Constify copy related functions #83091
• Final commenting period (FCP)
• Stabilization PR

Unresolved Questions

• None yet.

[RalfJung]

This got reverted again by #86003, but hopefully we can re-land it soon.

[RalfJung]

Sorry, I misread, this feature gate is not affected (but some others are).

[Finomnis]

Any news on this? I don't see anything holding it back; especially now that transmute itself is const.

EDIT: Never mind, I just saw #85769 (comment).

[RalfJung]

Since ptr.read() is const-stable nowadays, I think this can be stabilized as well. Feel free to open a PR. :)

Cc @rust-lang/wg-const-eval

[Finomnis]

@RalfJung I didn't do this before, I am reading the docs for how to do this, and there's an rfcbot final commenting period thing. Should this be done? If yes, how? I probably don't have the rights to do it.

[RalfJung]

You just need to prepare a PR. I can help get the FCP process started in the PR.