consistent wording

This commit is contained in:
Ralf Jung 2023-08-19 16:44:54 +02:00
parent 39b53dc204
commit 14625f5b3e
2 changed files with 4 additions and 4 deletions

View File

@ -648,8 +648,8 @@ impl<T: ?Sized> *const T {
/// such large allocations either.)
///
/// The requirement for pointers to be derived from the same allocated object is primarily
/// needed for `const`-compatibility: at compile-time, pointers into *different* allocated
/// objects do not have a known distance to each other. However, the requirement also exists at
/// needed for `const`-compatibility: the distance between pointers into *different* allocated
/// objects is not known at compile-time. However, the requirement also exists at
/// runtime and may be exploited by optimizations. If you wish to compute the difference between
/// pointers that are not guaranteed to be from the same allocation, use `(self as
/// usize).sub(origin as usize) / mem::size_of::<T>()`.

View File

@ -822,8 +822,8 @@ impl<T: ?Sized> *mut T {
/// such large allocations either.)
///
/// The requirement for pointers to be derived from the same allocated object is primarily
/// needed for `const`-compatibility: at compile-time, pointers into *different* allocated
/// objects do not have a known distance to each other. However, the requirement also exists at
/// needed for `const`-compatibility: the distance between pointers into *different* allocated
/// objects is not known at compile-time. However, the requirement also exists at
/// runtime and may be exploited by optimizations. If you wish to compute the difference between
/// pointers that are not guaranteed to be from the same allocation, use `(self as
/// usize).sub(origin as usize) / mem::size_of::<T>()`.