226edf64fa
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.
31 lines
968 B
Plaintext
31 lines
968 B
Plaintext
error: attribute value must be a literal
|
|
--> $DIR/key-value-expansion.rs:21:6
|
|
|
|
|
LL | bug!((column!()));
|
|
| ^^^^^^^^^^^
|
|
|
|
error: attribute value must be a literal
|
|
--> $DIR/key-value-expansion.rs:27:14
|
|
|
|
|
LL | bug!("bug" + stringify!(found));
|
|
| ^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
...
|
|
LL | bug!();
|
|
| ------ in this macro invocation
|
|
|
|
|
= note: this error originates in the macro `bug` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: attribute value must be a literal
|
|
--> $DIR/key-value-expansion.rs:48:23
|
|
|
|
|
LL | doc_comment! {format!("{coor}", coor = stringify!($t1)).as_str()}
|
|
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
...
|
|
LL | some_macro!(u8);
|
|
| --------------- in this macro invocation
|
|
|
|
|
= note: this error originates in the macro `some_macro` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: aborting due to 3 previous errors
|
|
|