Tracking Issue for `const_copy_from_slice`

[okaneco]

Feature gate: #![feature(const_copy_from_slice)]

This is a tracking issue for using <[T]>::copy_from_slice in const.

Public API

impl<T> [T] {
    pub const fn copy_from_slice(&mut self, src: &[T])
    where
        T: Copy;
}

Steps / History

• Implementation: Mark slice::copy_from_slice unstably const #131416
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[bjoernager]

The referenced function should be <[T]>::copy_from_slice (method of [T]) instead of slice::copy_from_slice (function in core::slice).

[RalfJung]

@rust-lang/libs-api @rust-lang/wg-const-eval this function has been stable since Rust 1.9, and can be fully implemented using already-const-stable facilities (largely, ptr::copy_nonoverlapping). I would say it is ready for const-stabilization. :)

impl<T> [T] {
    pub const fn copy_from_slice(&mut self, src: &[T])
    where
        T: Copy;
}

[dtolnay]

@rfcbot fcp merge

[rfcbot]

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

• @Amanieu
• @BurntSushi
• @dtolnay
• @joshtriplett
• @m-ou-se

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.

[rfcbot]

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