about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2015-10-16 20:35:51 +0000
committerbors <bors@rust-lang.org>2015-10-16 20:35:51 +0000
commitbe9104291391d9adff91c9ece2b562150979a899 (patch)
treeedc1b41fed96ee8365de952294b2c93f816dcd94
parent747d951e883978e1d3b92bdca2cac5845869bb78 (diff)
parent5736c1d90ad89a72d217762d74fe53907448a558 (diff)
downloadrust-be9104291391d9adff91c9ece2b562150979a899.tar.gz
rust-be9104291391d9adff91c9ece2b562150979a899.zip
Auto merge of #29082 - DenisKolodin:patch-3, r=alexcrichton
-rw-r--r--src/doc/nomicon/safe-unsafe-meaning.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/nomicon/safe-unsafe-meaning.md b/src/doc/nomicon/safe-unsafe-meaning.md
index f5d7023fad5..827ea255053 100644
--- a/src/doc/nomicon/safe-unsafe-meaning.md
+++ b/src/doc/nomicon/safe-unsafe-meaning.md
@@ -41,8 +41,8 @@ Some examples of unsafe functions:
 
 * `slice::get_unchecked` will perform unchecked indexing, allowing memory
   safety to be freely violated.
-* `ptr::offset` is an intrinsic that invokes Undefined Behavior if it is
-  not "in bounds" as defined by LLVM.
+* every raw pointer to sized type has intrinsic `offset` method that invokes
+  Undefined Behaviour if it is not "in bounds" as defined by LLVM.
 * `mem::transmute` reinterprets some value as having the given type,
   bypassing type safety in arbitrary ways. (see [conversions] for details)
 * All FFI functions are `unsafe` because they can do arbitrary things.