From: Tobias Bucher Date: Mon, 17 Sep 2018 16:34:15 +0000 (+0200) Subject: Adjust the docs of `from_raw_parts` to match the implementation X-Git-Url: https://git.lizzy.rs/?a=commitdiff_plain;h=ebffb672950dbf6d2a19364269f95b4bc3e40dc4;p=rust.git Adjust the docs of `from_raw_parts` to match the implementation --- diff --git a/src/libcore/slice/mod.rs b/src/libcore/slice/mod.rs index 3f43da9b3b6..0a719792c7f 100644 --- a/src/libcore/slice/mod.rs +++ b/src/libcore/slice/mod.rs @@ -3852,8 +3852,8 @@ fn may_have_side_effect() -> bool { false } /// them from other data. You can obtain a pointer that is usable as `data` /// for zero-length slices using [`NonNull::dangling()`]. /// -/// The total size of the slice must lower than `isize::MAX` **bytes** in -/// memory. See the safety documentation of [`pointer::offset`]. +/// The total size of the slice must be no larger than `isize::MAX` **bytes** +/// in memory. See the safety documentation of [`pointer::offset`]. /// /// # Caveat /// @@ -3892,8 +3892,8 @@ pub unsafe fn from_raw_parts<'a, T>(data: *const T, len: usize) -> &'a [T] { /// This function is unsafe for the same reasons as [`from_raw_parts`], as well /// as not being able to provide a non-aliasing guarantee of the returned /// mutable slice. `data` must be non-null and aligned even for zero-length -/// slices as with [`from_raw_parts`]. The total size of the slice must be -/// lower than `isize::MAX` **bytes** in memory. See the safety documentation +/// slices as with [`from_raw_parts`]. The total size of the slice must be no +/// larger than `isize::MAX` **bytes** in memory. See the safety documentation /// of [`pointer::offset`]. /// /// See the documentation of [`from_raw_parts`] for more details.