rust/tests/ui/check-cfg/allow-same-level.stderr

warning: unexpected `cfg` condition name: `FALSE`
  --> $DIR/allow-same-level.rs:7:7
   |
LL | #[cfg(FALSE)]
   |       ^^^^^
   |
   = help: expected names are: `debug_assertions`, `doc`, `doctest`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `unix`, `windows`
   = help: to expect this configuration use `--check-cfg=cfg(FALSE)`
   = note: see <https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/check-cfg.html> for more information about checking conditional configuration
   = note: `#[warn(unexpected_cfgs)]` on by default

warning: 1 warning emitted
check-cfg: mention the unexpected name and value in the primary message 2023-10-12 09:49:56 -05:00			warning: unexpected `cfg` condition name: `FALSE`
Improve allowness of the unexpected_cfgs lint 2022-02-27 15:26:24 -06:00			`--> $DIR/allow-same-level.rs:7:7`
			`\|`
			`LL \| #[cfg(FALSE)]`
			`\| ^^^^^`
			`\|`
Rearrange `default_configuration` and `CheckCfg::fill_well_known`. There are comments saying these two functions should be kept in sync, but they have very different structures, process symbols in different orders, and there are some inconsistencies. This commit reorders them so they're both mostly processing symbols in alphabetical order, which makes cross-checking them a lot easier. The commit also adds some macros to factor out repetitive code patterns. Plus it adds `sanitizer_cfi_normalize_{integers,pointers}` to `fill_well_known`, which were missing. The commit also moves the handling of `sym::test` out of `build_configuration` into `default_configuration`, where all the other symbols are handled. 2023-11-28 22:08:43 -06:00			= help: expected names are: `debug_assertions`, `doc`, `doctest`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `unix`, `windows`
Add more suggestion to unexpected cfg names and values 2023-11-22 09:50:24 -06:00			= help: to expect this configuration use `--check-cfg=cfg(FALSE)`
			`= note: see <https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/check-cfg.html> for more information about checking conditional configuration`
Improve allowness of the unexpected_cfgs lint 2022-02-27 15:26:24 -06:00			= note: `#[warn(unexpected_cfgs)]` on by default

			`warning: 1 warning emitted`