From 061cdec5dfefc91ce2ad00cef1435ce9b7b1db74 Mon Sep 17 00:00:00 2001 From: Philipp Gesang Date: Tue, 12 Aug 2014 21:30:02 +0200 Subject: [PATCH] guide-unsafe.md: fix wording Following a suggestion by Huon Wilson. --- src/doc/guide-unsafe.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/guide-unsafe.md b/src/doc/guide-unsafe.md index 34cec8d980a3d..2ff6305548083 100644 --- a/src/doc/guide-unsafe.md +++ b/src/doc/guide-unsafe.md @@ -137,7 +137,7 @@ explicitly with, respectively, `value as *const T` and `value as *mut T`). Going the opposite direction, from `*const` to a reference `&`, is not safe. A `&T` is always valid, and so, at a minimum, the raw pointer -`*const T` has to be a pointer to a valid instance of type `T`. Furthermore, +`*const T` has to point to a valid instance of type `T`. Furthermore, the resulting pointer must satisfy the aliasing and mutability laws of references. The compiler assumes these properties are true for any references, no matter how they are created, and so any conversion from