New upstream version 1.44.1+dfsg1

[rustc.git] / src / doc / reference / src / behavior-considered-undefined.md

diff --git a/src/doc/reference/src/behavior-considered-undefined.md b/src/doc/reference/src/behavior-considered-undefined.md
index f3a27ad63aad2834ece6e1d0c0b4922a3618ff12..89c318a0480480972df2081f00d2390d17a4bbc5 100644 (file)
--- a/src/doc/reference/src/behavior-considered-undefined.md
+++ b/src/doc/reference/src/behavior-considered-undefined.md
@@ -61,11 +61,11 @@ code.
 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 is important that the length metadata is never too
-large. In particular, allocations and therefore slices cannot be bigger than
-`isize::MAX` bytes.
+pointer value and the size of the pointee type (using `size_of_val`). 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 is important that the length
+metadata is never too large. In particular, allocations and therefore slices
+cannot be bigger than `isize::MAX` bytes.
 
 > **Note**: Undefined behavior affects the entire program. For example, calling
 > a function in C that exhibits undefined behavior of C means your entire