mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Emphasize semantic differences of Copy/Clone rather than impl

Browse Source
This commit is contained in:
Carol (Nichols || Goulding) 2016-05-23 12:58:42 -04:00
parent b4e123d3e0
commit d2ee6e04ab
1 changed files with 4 additions and 3 deletions

7
src/libcore/clone.rs

@ -48,9 +48,10 @@ use marker::Sized;
/// A common trait for the ability to explicitly duplicate an object.
///
/// Differs from `Copy` in that you can
/// define `Clone` to run arbitrary code, while you are not allowed to override
/// the implementation of `Copy` that only does a `memcpy`.
/// Differs from `Copy` in that `Copy` is implicit and extremely inexpensive, while
/// `Clone` is always explicit and may or may not be expensive. In order to enforce
/// these characteristics, Rust does not allow you to reimplement `Copy`, but you
/// may reimplement `Clone` and run arbitrary code.
///
/// Since `Clone` is more general than `Copy`, you can automatically make anything
/// `Copy` be `Clone` as well.