Update array documentation for Clone trait changes
This commit is contained in:
parent
db80da1c1a
commit
8528508aa0
1 changed files with 4 additions and 3 deletions
|
@ -284,7 +284,6 @@ mod prim_pointer { }
|
|||
/// Arrays of sizes from 0 to 32 (inclusive) implement the following traits if
|
||||
/// the element type allows it:
|
||||
///
|
||||
/// - [`Clone`][clone] (only if `T: `[`Copy`][copy])
|
||||
/// - [`Debug`][debug]
|
||||
/// - [`IntoIterator`][intoiterator] (implemented for `&[T; N]` and `&mut [T; N]`)
|
||||
/// - [`PartialEq`][partialeq], [`PartialOrd`][partialord], [`Eq`][eq], [`Ord`][ord]
|
||||
|
@ -299,8 +298,10 @@ mod prim_pointer { }
|
|||
/// entirely different types. As a stopgap, trait implementations are
|
||||
/// statically generated up to size 32.
|
||||
///
|
||||
/// Arrays of *any* size are [`Copy`][copy] if the element type is [`Copy`][copy]. This
|
||||
/// works because the [`Copy`][copy] trait is specially known to the compiler.
|
||||
/// Arrays of *any* size are [`Copy`][copy] if the element type is [`Copy`][copy]
|
||||
/// and [`Clone`][clone] if the element type is [`Clone`][clone]. This works
|
||||
/// because [`Copy`][copy] and [`Clone`][clone] traits are specially known
|
||||
/// to the compiler.
|
||||
///
|
||||
/// Arrays coerce to [slices (`[T]`)][slice], so a slice method may be called on
|
||||
/// an array. Indeed, this provides most of the API for working with arrays.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue