Skip to content

Tracking issue for slice_partition_at_index #55300

Description

@Mokosha

This is the tracking bug for the discussion outlined in rust-lang/rfcs#1470.

I'm working on implementing this in the libstd, and will add it as an unstable feature pending resolution of any comments that may arise in this thread. I plan to add comprehensive testing as well.

Activity

  1. nikic commented on Oct 24, 2018

    @nikic
    Contributor

    Just for the record, if someone needs this functionality right now, the order_stat crate provides an implementation of the Floyd-Rivest selection algorithm.

  2. added a commit that references this issue on Jan 23, 2019
  3. added a commit that references this issue on Mar 11, 2019
  4. scottmcm commented on Apr 2, 2019

    @scottmcm
    Member

    A thought: since we have sort and sort_unstable, should the method that got implemented be partition_unstable_at_index instead? Though I suppose there's no good stable way to do it...

  5. added 2 commits that reference this issue on Apr 2, 2019
  6. umanwizard commented on Aug 30, 2019

    @umanwizard
    Contributor

    Hi @Mokosha , is this expected to be stabilized eventually?

  7. added
    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
    and removed
    C-feature-requestCategory: A feature request, i.e: not implemented / a PR.
    on Sep 2, 2019
  8. changed the title [-]Feature Request: analog of C++'s std::nth_element for rust slices.[/-] [+]Tracking issue for slice_partition_at_index[/+] on Sep 2, 2019
  9. 34 remaining items

  10. jagill commented on Oct 7, 2020

    @jagill
    Contributor

    @Amanieu I'm happy to make the PR changing the name and stabilizing the issue, but I have a question: If we change the name, this will be breaking for anyone who's been using the current name. It this acceptable, or is there an aliasing step that will preserve behavior for those using the feature flag?

  11. scottmcm commented on Oct 7, 2020

    @scottmcm
    Member

    @jagill It's nightly so it's allowed, but to make it a bit easier on nightly users it's generally preferable to to stabilize it under a different feature gate name so the old method can be left there for a month or two before being removing.

  12. 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 Oct 9, 2020
  13. rfcbot commented on Oct 9, 2020

    @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.

    The RFC will be merged soon.

  14. added a commit that references this issue on Oct 12, 2020
    01ac5a9
  15. added a commit that references this issue on Oct 13, 2020
    c0d1e29
  16. added a commit that references this issue on Oct 13, 2020
    ec40181
  17. est31 commented on Jan 30, 2022

    @est31
    Member

    I've opened #93480 to remove the deprecated and unstable partition_at_index_* functions that were added to ease the transition to the stable feature.

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-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 RFCI-libs-radarLibs issues that are tracked on the team's radar.Libs-SmallLibs issues that are considered "small" or self-containedT-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