Move note about 0 gap to signed integers

Was accidentally placed on unsigned integers, where it is not relevant.
This commit is contained in:
Nikolai Vazquez 2022-03-10 17:52:48 -05:00
parent fe71c7431a
commit ecb7927050

View File

@ -996,10 +996,6 @@ macro_rules! nonzero_min_max_unsigned {
/// The smallest value that can be represented by this non-zero
/// integer type, 1.
///
/// Note: While most integer types are defined for every whole
/// number between `MIN` and `MAX`, signed non-zero integers are
/// a special case. They have a "gap" at 0.
///
/// # Examples
///
/// ```
@ -1015,10 +1011,6 @@ macro_rules! nonzero_min_max_unsigned {
/// integer type,
#[doc = concat!("equal to [`", stringify!($Int), "::MAX`].")]
///
/// Note: While most integer types are defined for every whole
/// number between `MIN` and `MAX`, signed non-zero integers are
/// a special case. They have a "gap" at 0.
///
/// # Examples
///
/// ```
@ -1042,6 +1034,10 @@ macro_rules! nonzero_min_max_signed {
/// integer type,
#[doc = concat!("equal to [`", stringify!($Int), "::MIN`].")]
///
/// Note: While most integer types are defined for every whole
/// number between `MIN` and `MAX`, signed non-zero integers are
/// a special case. They have a "gap" at 0.
///
/// # Examples
///
/// ```
@ -1057,6 +1053,10 @@ macro_rules! nonzero_min_max_signed {
/// integer type,
#[doc = concat!("equal to [`", stringify!($Int), "::MAX`].")]
///
/// Note: While most integer types are defined for every whole
/// number between `MIN` and `MAX`, signed non-zero integers are
/// a special case. They have a "gap" at 0.
///
/// # Examples
///
/// ```