From 5736c1d90ad89a72d217762d74fe53907448a558 Mon Sep 17 00:00:00 2001 From: DenisKolodin Date: Thu, 15 Oct 2015 23:57:23 +0300 Subject: [PATCH] Update explanation about offset method --- src/doc/nomicon/safe-unsafe-meaning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/doc/nomicon/safe-unsafe-meaning.md b/src/doc/nomicon/safe-unsafe-meaning.md index f5d7023fad5de..827ea255053c2 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.