diff options
| author | Ralf Jung <post@ralfj.de> | 2019-07-23 17:51:52 +0200 |
|---|---|---|
| committer | Ralf Jung <post@ralfj.de> | 2019-07-23 17:51:52 +0200 |
| commit | 65cf10d90276e40bd8cc27a79d6c6f0d13e0cc7a (patch) | |
| tree | c20cbf946908e2d40e55754cc10843ed0be4feed | |
| parent | dd5045ed630b7577296087f09f559bb9c08f68e2 (diff) | |
| download | rust-65cf10d90276e40bd8cc27a79d6c6f0d13e0cc7a.tar.gz rust-65cf10d90276e40bd8cc27a79d6c6f0d13e0cc7a.zip | |
word things more like we usually do
| -rw-r--r-- | src/libstd/primitive_docs.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libstd/primitive_docs.rs b/src/libstd/primitive_docs.rs index b79cfa3eead..d9a3da66a67 100644 --- a/src/libstd/primitive_docs.rs +++ b/src/libstd/primitive_docs.rs @@ -900,8 +900,8 @@ mod prim_usize { } /// For those familiar with pointers, a reference is just a pointer that is assumed to be /// aligned, not null, and pointing to memory containing a valid value of `T` - for example, /// `&bool` can only point to an allocation containing the integer values `1` (`true`) or `0` -/// (`false`), but the behavior of creating a `&bool` that points to an allocation containing -/// the value `3` is undefined. +/// (`false`), but creating a `&bool` that points to an allocation containing +/// the value `3` causes undefined behaviour. /// In fact, `Option<&T>` has the same memory representation as a /// nullable but aligned pointer, and can be passed across FFI boundaries as such. /// |
