os-rust/tests/ui/check-cfg/exhaustive-values.empty_cfg.stderr

warning: unexpected `cfg` condition value: `value`
  --> $DIR/exhaustive-values.rs:9:7
   |
LL | #[cfg(test = "value")]
   |       ^^^^----------
   |           |
   |           help: remove the value
   |
   = note: no expected value for `test`
   = 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 16:49:56 +02:00			warning: unexpected `cfg` condition value: `value`
MCP636: Adapt check-cfg tests to the new syntax 2023-05-01 14:16:38 +02:00			`--> $DIR/exhaustive-values.rs:9:7`
Add well known values to --check-cfg implementation 2022-02-25 16:10:26 +01:00			`\|`
			`LL \| #[cfg(test = "value")]`
Improve unexpected_cfgs lint when their is no value expected 2022-03-03 15:56:19 +01:00			`\| ^^^^----------`
			`\| \|`
			`\| help: remove the value`
Add well known values to --check-cfg implementation 2022-02-25 16:10:26 +01:00			`\|`
			= note: no expected value for `test`
bless ui tests 2022-09-18 19:55:36 +04:00			= note: `#[warn(unexpected_cfgs)]` on by default
Add well known values to --check-cfg implementation 2022-02-25 16:10:26 +01:00
Update --check-cfg tests that had old --cfg warning 2023-11-02 17:06:32 +01:00			`warning: 1 warning emitted`
Add well known values to --check-cfg implementation 2022-02-25 16:10:26 +01:00