@@ -42,11 +42,11 @@ use core::num::NonZeroU32;
4242///
4343/// Although this should not be observable to its users, a `NonMaxU32` whose
4444/// value is `n` is a newtype around a [`NonZeroU32`] whose value is `n + 1`.
45- /// This way, the range of values that `NonMaxU32` can represent, `0..=u32::MAX
46- /// - 1`, is mapped to the range `1..=u32::MAX`, which is the range that
47- /// [`NonZeroU32`] can represent. (And conversely, since [`u32`] addition wraps
48- /// around, the value unrepresentable in `NonMaxU32`, [`u32::MAX`], becomes the
49- /// value unrepresentable in [`NonZeroU32`], `0`.)
45+ /// This way, the range of values that `NonMaxU32` can represent,
46+ /// `0..=u32::MAX - 1`, is mapped to the range `1..=u32::MAX`, which is the
47+ /// range that /// [`NonZeroU32`] can represent. (And conversely, since
48+ /// [`u32`] addition wraps around, the value unrepresentable in `NonMaxU32`,
49+ /// [`u32::MAX`], becomes the value unrepresentable in [`NonZeroU32`], `0`.)
5050///
5151/// [`NonZeroU32`]: core::num::NonZeroU32
5252#[ derive( Copy , Clone , Eq , PartialEq , Ord , PartialOrd , Hash ) ]
0 commit comments