Repository navigation
Tracking Issue for const_array_as_mut_slice #133333
Copy link
Copy link
Closed
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-api[DEPRECATED; DO NOT USE][DEPRECATED; DO NOT USE]
Description
Activity
- addedC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-api[DEPRECATED; DO NOT USE][DEPRECATED; DO NOT USE]
on Nov 22, 2024 I've
r+'ed the unstable implementation. Given that this is as trivial as it gets, I think it makes sense for this to be stabilized without any further consideration. cc @rust-lang/libs-api for possible FCPI'll get around to the stabilisation PR, then. :)
Up to you, as a stabilization PR is of course simple. I would be surprised if the team didn't want to stabilize it, but it's also not up to me.
Sure. If anything, it can just sit idle until the (I'm assuming inevitable) FCP has passed – or whatever else happens.
- added a commit that references this issue
on Nov 23, 2024 I've opened a PR to stabilize this: #140066.
We'll need to start an FCP.
- added a commit that references this issue
on May 25, 2025
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-api[DEPRECATED; DO NOT USE][DEPRECATED; DO NOT USE]
Add the
constspecifier to<[T; N]>::as_mut_slice.Public API
Steps / History
<[T; N]>::as_mut_slicewith theconstspecifier. #133332<[T; N]>::as_mut_sliceasconst#140066Unresolved Questions