Skip to content

Tracking Issue for array_methods #76118

@LukasKalbertodt

Description

@LukasKalbertodt
Member

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:

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)

Unresolved Questions

  • Use the names each_ref and each_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.

Activity

added
T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.
B-unstableBlocker: Implemented in the nightly compiler and unstable.
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
on Aug 30, 2020
LukasKalbertodt

LukasKalbertodt commented on Aug 30, 2020

@LukasKalbertodt
MemberAuthor

Just for the protocol, I plan to add the following methods in the near future:

(discussions about the usefulness of those method should be had in the dedicated PR threads and not here)

added a commit that references this issue on Sep 3, 2020
10aa3d3
added
Libs-TrackedLibs issues that are tracked on the team's project board.
on Sep 10, 2020
usbalbin

usbalbin commented on Nov 29, 2020

@usbalbin
Contributor

@LukasKalbertodt I have opened PR #79451 for zip, saw your comment just now.

38 remaining items

pravic

pravic commented on Oct 20, 2023

@pravic
Contributor

Any news about this?

added
final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
and removed
proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
on Jan 16, 2024
rfcbot

rfcbot commented on Jan 16, 2024

@rfcbot
Collaborator

🔔 This is now entering its final comment period, as per the review above. 🔔

added and removed
final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
on Jan 26, 2024
rfcbot

rfcbot commented on Jan 26, 2024

@rfcbot
Collaborator

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

This will be merged soon.

added 2 commits that reference this issue on Jan 26, 2024
94723d4
c9ab37b
added a commit that references this issue on Jan 27, 2024
ea29124
added a commit that references this issue on Jan 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-arrayArea: `[T; N]`A-sliceArea: `[T]`B-unstableBlocker: Implemented in the nightly compiler and unstable.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCLibs-TrackedLibs issues that are tracked on the team's project board.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @pravic@jplatte@LunaBorowska@Aaron1011@pierzchalski

      Issue actions

        Tracking Issue for `array_methods` · Issue #76118 · rust-lang/rust