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.
15 lines
334 B
Plaintext
15 lines
334 B
Plaintext
error: attribute value must be a literal
|
|
--> $DIR/unused-item-in-attr.rs:1:7
|
|
|
|
|
LL | #[w = { extern crate alloc; }]
|
|
| ^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
error: cannot find attribute `w` in this scope
|
|
--> $DIR/unused-item-in-attr.rs:1:3
|
|
|
|
|
LL | #[w = { extern crate alloc; }]
|
|
| ^
|
|
|
|
error: aborting due to 2 previous errors
|
|
|