From 2b7f8a0604aa7fe4e7f8b9c8cf0c9d0670342e0d Mon Sep 17 00:00:00 2001 From: Josh Triplett Date: Mon, 17 Mar 2025 13:49:10 -0700 Subject: [PATCH] Use `cfg(false)` instead of `cfg(FALSE)` --- src/items/enumerations.md | 2 +- src/tokens.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/items/enumerations.md b/src/items/enumerations.md index d9d16bf0a..10de33e19 100644 --- a/src/items/enumerations.md +++ b/src/items/enumerations.md @@ -353,7 +353,7 @@ macro_rules! mac_variant { mac_variant! { E } // This is allowed, since it is removed before being validated. -#[cfg(FALSE)] +#[cfg(false)] enum E { pub U, pub(crate) T(u8), diff --git a/src/tokens.md b/src/tokens.md index fc2205ad3..df9902f6d 100644 --- a/src/tokens.md +++ b/src/tokens.md @@ -589,7 +589,7 @@ Note that `-1i8`, for example, is analyzed as two tokens: `-` followed by `1i8`. Examples of integer literals which are not accepted as literal expressions: ```rust -# #[cfg(FALSE)] { +# #[cfg(false)] { 0invalidSuffix; 123AFB43; 0b010a; @@ -676,7 +676,7 @@ Note that `-1.0`, for example, is analyzed as two tokens: `-` followed by `1.0`. Examples of floating-point literals which are not accepted as literal expressions: ```rust -# #[cfg(FALSE)] { +# #[cfg(false)] { 2.0f80; 2e5f80; 2e5e6;