Skip to content

Tracking issue for DoubleEndedIterator::nth_back #56995

Closed

Description

@clarfonthey

PR: #56802

Currently, none of the standard adapters specialise this except for Rev, which trivially swaps nth and nth_back. These should probably be added before this feature is stabilised, and it's probably a good idea to check if nth should be specialised for any of these adapters too.

Additionally, the standard collection iterators should specialise this where appropriate.

Activity

  1. clarfonthey commented on Dec 19, 2018

    @clarfonthey
    ContributorAuthor

    Ping @alexcrichton (or whomever) to add the appropriate labels to this.

  2. added
    T-libs-api[DEPRECATED; DO NOT USE]
    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 Dec 19, 2018
  3. SimonSapin commented on Apr 24, 2019

    @SimonSapin
    Contributor

    #54054 tracks adding more impls of nth_back, but I think this doesn’t need to block stabilization.

    @rfcbot fcp merge

  4. rfcbot commented on Apr 24, 2019

    @rfcbot

    Team member @SimonSapin 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.
    on Apr 24, 2019
  6. rfcbot commented on Apr 30, 2019

    @rfcbot

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

  7. 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 Apr 30, 2019
  8. rfcbot commented on May 10, 2019

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

  9. removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on May 10, 2019
  10. added a commit that references this issue on May 30, 2019
  11. added a commit that references this issue on May 31, 2019
  12. sallyyu0 commented on Nov 11, 2019

    @sallyyu0

    Hello, I'm getting this error suddenly which points to this issue. Any clue how to fix it? Thanks!

    Compiling lock_api v0.3.1
    error[E0658]: use of unstable library feature 'iter_nth_back'
    --> /home/zzz/.cargo/registry/src/github.life-white.uk-1ecc6299db9ec823/ipnet-2.1.0/src/ipext.rs:638:5
    |
    638 | / fn nth_back(&mut self, n: usize) -> OptionSelf::Item {
    639 | | match *self {
    640 | | IpAddrRange::V4(ref mut a) => a.nth_back(n).map(IpAddr::V4),
    641 | | IpAddrRange::V6(ref mut a) => a.nth_back(n).map(IpAddr::V6),
    642 | | }
    643 | | }
    | |_____^
    |
    = note: for more information, see #56995

    error[E0658]: use of unstable library feature 'iter_nth_back'

  13. clarfonthey commented on Nov 11, 2019

    @clarfonthey
    ContributorAuthor

    Are you using an up to date nightly?

  14. koalatux commented on Nov 11, 2019

    @koalatux
    Contributor

    error[E0658]: use of unstable library feature 'iter_nth_back'

    nth_back() has been stabilized in Rust 1.37.0, have you tried updating to a recent version of Rust?

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

    B-unstableBlocker: Implemented in the nightly compiler and unstable.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