granite-rust/tests/ui/malformed/malformed-interpolated.stderr

error: suffixed literals are not allowed in attributes
  --> $DIR/malformed-interpolated.rs:12:8
   |
LL | check!(0u8);
   |        ^^^
   |
   = help: instead of using a suffixed literal (`1u8`, `1.0f32`, etc.), use an unsuffixed version (`1`, `1.0`, etc.)

error: attribute value must be a literal
  --> $DIR/malformed-interpolated.rs:13:8
   |
LL | check!(-0);
   |        ^^

error: attribute value must be a literal
  --> $DIR/malformed-interpolated.rs:14:8
   |
LL | check!(0 + 0);
   |        ^^^^^

error: aborting due to 3 previous errors
Restrict value in key-value attributes to literals 2019-01-04 02:57:11 +03:00			`error: suffixed literals are not allowed in attributes`
Accept arbitrary expressions in key-value attributes at parse time 2020-11-07 16:09:40 +03:00			`--> $DIR/malformed-interpolated.rs:12:8`
Restrict value in key-value attributes to literals 2019-01-04 02:57:11 +03:00			`\|`
Simplify conversions between tokens and semantic literals 2019-05-10 03:00:51 +03:00			`LL \| check!(0u8);`
			`\| ^^^`
Restrict value in key-value attributes to literals 2019-01-04 02:57:11 +03:00			`\|`
Add backticks in appropriate places 2020-01-10 14:57:36 +00:00			= help: instead of using a suffixed literal (`1u8`, `1.0f32`, etc.), use an unsuffixed version (`1`, `1.0`, etc.)
Restrict value in key-value attributes to literals 2019-01-04 02:57:11 +03:00
Improve an error involving attribute values. Attribute values must be literals. The error you get when that doesn't hold is pretty bad, e.g.: ``` unexpected expression: 1 + 1 ``` You also get the same error if the attribute value is a literal, but an invalid literal, e.g.: ``` unexpected expression: "foo"suffix ``` This commit does two things. - Changes the error message to "attribute value must be a literal", which gives a better idea of what the problem is and how to fix it. It also no longer prints the invalid expression, because the carets below highlight it anyway. - Separates the "not a literal" case from the "invalid literal" case. Which means invalid literals now get the specific error at the literal level, rather than at the attribute level. 2023-12-12 09:55:50 +11:00			`error: attribute value must be a literal`
Accept arbitrary expressions in key-value attributes at parse time 2020-11-07 16:09:40 +03:00			`--> $DIR/malformed-interpolated.rs:13:8`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 15:56:47 +02:00			`\|`
Accept arbitrary expressions in key-value attributes at parse time 2020-11-07 16:09:40 +03:00			`LL \| check!(-0);`
			`\| ^^`
Restrict value in key-value attributes to literals 2019-01-04 02:57:11 +03:00
Improve an error involving attribute values. Attribute values must be literals. The error you get when that doesn't hold is pretty bad, e.g.: ``` unexpected expression: 1 + 1 ``` You also get the same error if the attribute value is a literal, but an invalid literal, e.g.: ``` unexpected expression: "foo"suffix ``` This commit does two things. - Changes the error message to "attribute value must be a literal", which gives a better idea of what the problem is and how to fix it. It also no longer prints the invalid expression, because the carets below highlight it anyway. - Separates the "not a literal" case from the "invalid literal" case. Which means invalid literals now get the specific error at the literal level, rather than at the attribute level. 2023-12-12 09:55:50 +11:00			`error: attribute value must be a literal`
Accept arbitrary expressions in key-value attributes at parse time 2020-11-07 16:09:40 +03:00			`--> $DIR/malformed-interpolated.rs:14:8`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 15:56:47 +02:00			`\|`
Accept arbitrary expressions in key-value attributes at parse time 2020-11-07 16:09:40 +03:00			`LL \| check!(0 + 0);`
			`\| ^^^^^`
Restrict value in key-value attributes to literals 2019-01-04 02:57:11 +03:00
			`error: aborting due to 3 previous errors`