[Tracking]: Pursue stabilization for Rust RFC 2972: "Constrained Naked Functions"

[bstrie]

Is there an existing issue for this?

• I have searched the existing issues

Description

In service of getting off of the nightly Rust toolchain and onto the stable one, we need upstream Rust to finish stabilizing some of the necessary features that we rely on. This issue tracks the stabilization of one such feature, constrained naked functions: rust-lang/rust#90957

Acceptance Criteria

This issue can be closed when rust-lang/rust#90957 is closed.

Suggestions for a technical implementation

No response

[bstrie]

Status update: the Rust lang team has voted to officially supersede RFC 1201 (the original Naked Functions RFC) with RFC 2972 (Constrained Naked Functions), closing rust-lang/rust#32408 and removing one obstacle to stabilization.

I have filed a stabilization report for RFC 2972 at rust-lang/rust#90957 (comment) , which needs one more vote from a lang team member before it can enter FCP. However, before that can happen we must also resolve one new concern regarding the compatibility of #[naked] with various other attributes; to resolve this concern I have an in-progress PR at rust-lang/rust#93809 (only a medium priority for me at the moment).

At this point, I anticipate that naked functions will reach stable as of Rust 1.61 (scheduled for stable release 2022-05-19) at the earliest.

[dpal]

We are not going to continue this effort due to the existing alternative solution.