Skip to content

Tracking issue for const Pin methods #76654

New issue
Jump to bottom
New issue
Jump to bottom
Closed
Closed
Tracking issue for const Pin methods#76654
Labels
A-const-evalArea: Constant evaluation, covers all const contexts (static, const fn, ...)T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.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.
@CDirkx

Description

@CDirkx
CDirkx
opened on Sep 12, 2020

Constify methods of core::pin::Pin under the feature const_pin.

Implementation: #76655

Methods in const_pin (stable since #130136):

  • new
  • new_unchecked
  • get_ref
  • into_ref
  • get_mut
  • get_unchecked_mut
  • static_ref
  • static_mut

Methods in const_pin2:

  • into_inner
  • into_inner_unchecked

The const_pin2 methods will need #[rustc_allow_const_fn_unstable(const_precise_live_drops)] but that has been approved here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    A-const-evalArea: Constant evaluation, covers all const contexts (static, const fn, ...)T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.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