New upstream version 1.46.0~beta.2+dfsg1

[rustc.git] / src / doc / nomicon / src / what-unsafe-does.md

diff --git a/src/doc/nomicon/src/what-unsafe-does.md b/src/doc/nomicon/src/what-unsafe-does.md
index 7f13f93aacc341ba181d146bd7da0afa3b8feef9..f89fb82236ca33dbb3e3e4fc014f5b444a020eb7 100644 (file)
--- a/src/doc/nomicon/src/what-unsafe-does.md
+++ b/src/doc/nomicon/src/what-unsafe-does.md
@@ -30,14 +30,13 @@ language cares about is preventing the following things:
     * a `char` outside the ranges [0x0, 0xD7FF] and [0xE000, 0x10FFFF]
     * a `!` (all values are invalid for this type)
     * an integer (`i*`/`u*`), floating point value (`f*`), or raw pointer read from
-      [uninitialized memory][]
+      [uninitialized memory][], or uninitialized memory in a `str`.
     * a reference/`Box` that is dangling, unaligned, or points to an invalid value.
     * a wide reference, `Box`, or raw pointer that has invalid metadata:
         * `dyn Trait` metadata is invalid if it is not a pointer to a vtable for
           `Trait` that matches the actual dynamic trait the pointer or reference points to
         * slice metadata is invalid if the length is not a valid `usize`
           (i.e., it must not be read from uninitialized memory)
-    * a `str` that isn't valid UTF-8
     * a type with custom invalid values that is one of those values, such as a
       `NonNull` that is null. (Requesting custom invalid values is an unstable
       feature, but some stable libstd types, like `NonNull`, make use of it.)
@@ -49,11 +48,11 @@ A reference/pointer is "dangling" if it is null or not all of the bytes it
 points to are part of the same allocation (so in particular they all have to be
 part of *some* allocation). The span of bytes it points to is determined by the
 pointer value and the size of the pointee type. As a consequence, if the span is
-empty, "dangling" is the same as "non-null". Note that slices point to their
-entire range, so it's important that the length metadata is never too large
-(in particular, allocations and therefore slices cannot be bigger than
-`isize::MAX` bytes). If for some reason this is too cumbersome, consider using
-raw pointers.
+empty, "dangling" is the same as "non-null". Note that slices and strings point
+to their entire range, so it's important that the length metadata is never too
+large (in particular, allocations and therefore slices and strings cannot be
+bigger than `isize::MAX` bytes). If for some reason this is too cumbersome,
+consider using raw pointers.
 
 That's it. That's all the causes of Undefined Behavior baked into Rust. Of
 course, unsafe functions and traits are free to declare arbitrary other