From d8d3761899720dd07a4be84d455f1ab1ee2f9f34 Mon Sep 17 00:00:00 2001 From: Huon Wilson Date: Wed, 11 Feb 2015 13:58:11 +1100 Subject: [PATCH] Tweak wording of copy_nonoverlapping_memory to remove misleading 'allocated'. It doesn't have to be a literal memory allocation (ala malloc), e.g. it can be in static memory, so saying "allocated" is mildly misleading. --- src/libcore/intrinsics.rs | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/libcore/intrinsics.rs b/src/libcore/intrinsics.rs index 5562845e11d6f..050c144b74299 100644 --- a/src/libcore/intrinsics.rs +++ b/src/libcore/intrinsics.rs @@ -262,11 +262,12 @@ extern "rust-intrinsic" { /// /// # Safety /// - /// Beyond requiring that both regions of memory be allocated, it is Undefined Behaviour - /// for source and destination to overlap. Care must also be taken with the ownership of - /// `src` and `dst`. This method semantically moves the values of `src` into `dst`. - /// However it does not drop the contents of `dst`, or prevent the contents of `src` - /// from being dropped or used. + /// Beyond requiring that the program must be allowed to access both regions + /// of memory, it is Undefined Behaviour for source and destination to + /// overlap. Care must also be taken with the ownership of `src` and + /// `dst`. This method semantically moves the values of `src` into `dst`. + /// However it does not drop the contents of `dst`, or prevent the contents + /// of `src` from being dropped or used. /// /// # Examples ///