Skip to content

Tracking Issue for slice::split_at in const context #101158

Closed

Description

@tspiteri

Feature gate: #![feature(const_slice_split_at_not_mut)]

This is a tracking issue for usage of slice::split_at in const context.

Public API

impl<T> [T] {
    pub const fn split_at(&self, mid: usize) -> (&[T], &[T]);
}

Steps / History

Unresolved Questions

  • None yet.

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    T-libs-api[DEPRECATED; DO NOT USE]
    on Aug 29, 2022
  2. added 2 commits that reference this issue on Aug 30, 2022
  3. m-ou-se commented on May 1, 2023

    @m-ou-se
    Member

    @rfcbot merge

    cc @rust-lang/wg-const-eval

  4. rfcbot commented on May 1, 2023

    @rfcbot

    Team member @m-ou-se has proposed to merge this. The next step is review by the rest of the tagged team members:

    No concerns currently listed.

    Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

    See this document for info about what commands tagged team members can give me.

  5. added
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.
    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 May 1, 2023
  6. rfcbot commented on May 4, 2023

    @rfcbot

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

  7. added
    to-announceAnnounce this issue on triage meeting
    and removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on May 14, 2023
  8. rfcbot commented on May 14, 2023

    @rfcbot

    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.

  9. added a commit that references this issue on May 15, 2023
  10. scottmcm commented on May 19, 2023

    @scottmcm
    Member

    Stabilization PR landed; closing.

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

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-api[DEPRECATED; DO NOT USE]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

      No branches or pull requests

      Issue actions