Skip to content

Expose core::intrinsics::volatile_copy_nonoverlapping_memory as core::ptr::volatile_copy_nonoverlapping #58041

Description

@joshlf

View all comments

I propose that we expose core::intrinsics::volatile_copy_nonoverlapping_memory as the stable core::ptr::volatile_copy_nonoverlapping. It might make sense to stabilize other intrinsics while we're at it; I only mention this one in particular because I have a use case for it.

Is a discussion here sufficient, or should I submit an RFC?

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-feature-requestCategory: A feature request, i.e: not implemented / a PR.T-langRelevant to the language teamT-libsRelevant to the library team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions