Description
This is a tracking issue for a couple of basic methods on arrays. The feature gate for the issue is #![feature(array_methods)]
. Currently, this includes the following methods:
as_slice
,as_mut_slice
Add[T; N]::as_[mut_]slice
#76120each_ref
,each_mut
Add[T; N]::each_ref
and[T; N]::each_mut
#75490
Note: these methods were all collected under the same array_methods
feature name as I suspect many (often small) methods to be added to array in the near future. Creating a new feature and tracking issue for each seems overkill. We can still split off some methods into dedicated features later, if required.
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
- Decide what set of methods to stabilize in the first round
- Change feature names of all methods that are not yet stabilized to something specific
- Adjust documentation (see instructions on rustc-dev-guide)
- Stabilization PR (see instructions on rustc-dev-guide)
Unresolved Questions
- Use the names
each_ref
andeach_mut
or change it to something else? Alternatives:each_as_ref
/each_as_mut
,as_refs
/as_mut_refs
. See PR Add[T; N]::each_ref
and[T; N]::each_mut
#75490 for the name discussion.