rust/tests/ui/attributes/issue-90873.rs

#![u=||{static d=||1;}]
//~^ attribute value must be a literal
//~| cannot find attribute `u` in this scope
//~| missing type for `static` item

#![a={impl std::ops::Neg for i8 {}}]
//~^ ERROR attribute value must be a literal
//~| ERROR cannot find attribute `a` in this scope
//~| ERROR `main` function not found in crate `issue_90873`
Do not visit attributes in `ItemLowerer`. By default, AST visitors visit expressions that appear in key-value attributes. Those expressions should not be lowered to HIR, as they do not correspond to actually compiled code. Since an attribute cannot produce meaningful HIR, just skip them altogether. 2021-11-21 09:16:02 -06:00			`#![u=\|\|{static d=\|\|1;}]`
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-11 16:55:50 -06:00			`//~^ attribute value must be a literal`
Do not visit attributes in `ItemLowerer`. By default, AST visitors visit expressions that appear in key-value attributes. Those expressions should not be lowered to HIR, as they do not correspond to actually compiled code. Since an attribute cannot produce meaningful HIR, just skip them altogether. 2021-11-21 09:16:02 -06:00			//~\| cannot find attribute `u` in this scope
			//~\| missing type for `static` item
Do not visit attributes in `LateResolutionVisitor`. 2021-11-24 16:07:13 -06:00
			`#![a={impl std::ops::Neg for i8 {}}]`
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-11 16:55:50 -06:00			`//~^ ERROR attribute value must be a literal`
Do not visit attributes in `LateResolutionVisitor`. 2021-11-24 16:07:13 -06:00			//~\| ERROR cannot find attribute `a` in this scope
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be worse. This change will make it so that VSCode will not underline the whole file when `main` is missing, so other errors will be visible. 2022-01-20 18:15:39 -06:00			//~\| ERROR `main` function not found in crate `issue_90873`