Skip to content

Tracking Issue for const_intrinsic_copy #80697

@usbalbin

Description

@usbalbin
Contributor

Feature gate: #![feature(const_intrinsic_copy)]

This is a tracking issue for making the functions ptr::copy and ptr::copy_nonoverlapping as well as some related functions const fn.

Public API

mod ptr {
    pub const unsafe fn copy_nonoverlapping<T>(src: *const T, dst: *mut T, count: usize);
    pub const unsafe fn copy<T>(src: *const T, dst: *mut T, count: usize);
}

impl *const T {
    pub const unsafe fn copy_to(self, dest: *mut T, count: usize);
    pub const unsafe fn copy_to_nonoverlapping(self, dest: *mut T, count: usize);
}

impl *mut T {
    pub const unsafe fn copy_to(self, dest: *mut T, count: usize);
    pub const unsafe fn copy_to_nonoverlapping(self, dest: *mut T, count: usize);

    pub const unsafe fn copy_from(self, src: *const T, count: usize);
    pub const unsafe fn copy_from_nonoverlapping(self, src: *const T, count: usize);
}

Steps / History

Activity

added
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.
on Jan 4, 2021
added a commit that references this issue on Jan 5, 2021

Auto merge of rust-lang#80699 - usbalbin:const_copy_tracking_issue, r…

added
Libs-TrackedLibs issues that are tracked on the team's project board.
on Jan 6, 2021
usbalbin

usbalbin commented on Mar 4, 2021

@usbalbin
ContributorAuthor

@RalfJung with #81238 merged, is the concern about "bringing back debug assertions" resolved as - we won't bring them back?

RalfJung

RalfJung commented on Mar 5, 2021

@RalfJung
Member

Yeah I guess for now we won't bring them back.

RalfJung

RalfJung commented on Jun 14, 2021

@RalfJung
RalfJung

RalfJung commented on Jun 14, 2021

@RalfJung
joshtriplett

joshtriplett commented on Jan 26, 2022

@joshtriplett
Member

Seems reasonable, assuming that @rust-lang/wg-const-eval is fine with it.

@rfcbot merge
@rfcbot concern confirm-with-wg-const-eval

rfcbot

rfcbot commented on Jan 26, 2022

@rfcbot
Collaborator

Team member @joshtriplett has proposed to merge this. The next step is review by the rest of the tagged team members:

Concerns:

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.

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 Jan 26, 2022

33 remaining items

Loading
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 RFCLibs-TrackedLibs issues that are tracked on the team's project board.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @joshtriplett@RalfJung@m-ou-se@dtolnay@apiraino

      Issue actions

        Tracking Issue for const_intrinsic_copy · Issue #80697 · rust-lang/rust