Skip to content

Tracking Issue for NonNull<[T]>::slice_from_raw_parts #71941

Closed
#97506
Closed
Tracking Issue for NonNull<[T]>::slice_from_raw_parts#71941
#97506
Labels
A-raw-pointersArea: raw pointers, MaybeUninit, NonNullA-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.

Description

@SimonSapin
SimonSapin
opened on May 6, 2020

This is a tracking issue for the NonNull<[T]>::slice_from_raw_parts method proposed in PR #71940.
The feature gates for the issue are #![feature(nonnull_slice_from_raw_parts)], and #![feature(const_nonnull_slice_from_raw_parts)] for using as a const fn.

API

impl<T> NonNull<[T]> {
  pub const fn slice_from_raw_parts(data: NonNull<T>, len: usize) -> Self;
}

Docs: https://doc.rust-lang.org/stable/std/ptr/struct.NonNull.html#method.slice_from_raw_parts

Steps

Activity

  1. SimonSapin
    added
    T-libs-api[DEPRECATED; DO NOT USE]
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on May 6, 2020
  2. JohnTitor
    added
    B-unstableBlocker: Implemented in the nightly compiler and unstable.
    on May 6, 2020
  3. KodrAus
    added
    I-nominated
    A-sliceArea: `[T]`
    Libs-SmallLibs issues that are considered "small" or self-contained
    I-libs-radarLibs issues that are tracked on the team's radar.
    A-raw-pointersArea: raw pointers, MaybeUninit, NonNull
    on Jul 29, 2020
  4. m-ou-se
    removed
    I-nominated
    on Dec 8, 2020

  5. m-ou-se commented on Mar 12, 2022

    @m-ou-se
    m-ou-se
    on Mar 12, 2022
    Member

    @rfcbot merge

  6. rfcbot commented on Mar 12, 2022

    @rfcbot
    rfcbot
    on Mar 12, 2022

    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.

  7. rfcbot
    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 Mar 12, 2022

  8. bstrie commented on Apr 7, 2022

    @bstrie
    bstrie
    on Apr 7, 2022
    Contributor

    I'm willing to file the stabilization report for this if the library team is on board for stabilization.

  9. yaahc commented on Apr 7, 2022

    @yaahc
    yaahc
    on Apr 7, 2022
    Member

    I'm willing to file the stabilization report for this if the library team is on board for stabilization.

    I'd certainly appreciate one!

  10. rfcbot
    added
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on Apr 7, 2022

  11. rfcbot commented on Apr 7, 2022

    @rfcbot
    rfcbot
    on Apr 7, 2022

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

  12. rfcbot
    removed
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    on Apr 7, 2022
  13. rfcbot
    added
    finished-final-comment-periodThe final comment period is finished for this PR / Issue.
    and removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on Apr 17, 2022

  14. rfcbot commented on Apr 17, 2022

    @rfcbot
    rfcbot
    on Apr 17, 2022

    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.

  15. rfcbot
    added
    to-announceAnnounce this issue on triage meeting
    on Apr 17, 2022
  16. apiraino
    removed
    to-announceAnnounce this issue on triage meeting
    on Apr 21, 2022
  17. Dylan-DPC
    added a commit that references this issue on Mar 27, 2023

    Rollup merge of rust-lang#97506 - JohnTitor:stabilize-nonnull-slice-f…

    f13a541
  18. matthiaskrgr
    added a commit that references this issue on Mar 27, 2023

    Rollup merge of rust-lang#97506 - JohnTitor:stabilize-nonnull-slice-f…

    102bbbd
  19. bors
    closed this as completedin 102bbbdon Mar 27, 2023
  20. thomcc
    added a commit that references this issue on Jun 1, 2023

    Rollup merge of #97506 - JohnTitor:stabilize-nonnull-slice-from-raw-p…

    3c508e1
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-raw-pointersArea: raw pointers, MaybeUninit, NonNullA-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