Skip to content

Tracking Issue for non_null_from_ref #130823

Closed

Description

@bjoernager

Feature gate: #![feature(non_null_from_ref)]

This is a tracking issue for adding the convenience constructors from_ref and from_mut to core::ptr::NonNull.

Public API

// core::ptr

impl<T: ?Sized> NonNull<T> {
    pub const fn from_ref(r: &T) -> Self;

    pub const fn from_mut(r: &mut T) -> Self;
}

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 Sep 25, 2024
  2. added a commit that references this issue on Oct 16, 2024
  3. added a commit that references this issue on Oct 16, 2024
  4. smalis-msft commented on Jan 30, 2025

    @smalis-msft

    Is there anything blocking these from stabilization? They seem pretty straightforward.

  5. bjoernager commented on Jan 30, 2025

    @bjoernager
    ContributorAuthor

    Nope, nothing that I'm aware of (other than the FCP).

  6. m-ou-se commented on Feb 19, 2025

    @m-ou-se
    Member

    @rfcbot merge

  7. rfcbot commented on Feb 19, 2025

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

  8. 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 Feb 19, 2025
  9. mathisbot commented on Apr 30, 2025

    @mathisbot
  10. mathisbot commented on Apr 30, 2025

    @mathisbot
    Contributor

    Stabilization PR: #140511

  11. 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 May 6, 2025
  12. rfcbot commented on May 6, 2025

    @rfcbot

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

  13. added and removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on May 16, 2025
  14. rfcbot commented on May 16, 2025

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

  15. added a commit that references this issue on May 18, 2025
  16. added a commit that references this issue on May 18, 2025
  17. tgross35 commented on Jun 9, 2025

    @tgross35
    Member

    Stabilized in #140511

  18. added this to the 1.89.0 milestone on Jul 17, 2025
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.

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions