rust/tests/ui/attributes/unknown-attr.rs

// Unknown attributes fall back to unstable custom attributes.

#![feature(custom_inner_attributes)]

#![mutable_doc]
//~^ ERROR cannot find attribute `mutable_doc` in this scope

#[dance] mod a {}
//~^ ERROR cannot find attribute `dance` in this scope

#[dance] fn main() {}
//~^ ERROR cannot find attribute `dance` in this scope
Improve wording. 2019-09-07 20:34:24 -05:00			`// Unknown attributes fall back to unstable custom attributes.`
Add test for unknown attribute lint 2013-11-11 02:51:27 -06:00
Remove some more `#![feature(custom_attribute)]`s 2019-06-08 09:35:54 -05:00			`#![feature(custom_inner_attributes)]`
Add test for unknown attribute lint 2013-11-11 02:51:27 -06:00
resolve: Use `feature(custom_attribute)` fallback only if the feature is enabled Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them. It also helps with unifying diagnostics for unresolved macros. 2019-07-11 17:00:20 -05:00			`#![mutable_doc]`
resolve: Tweak "cannot find" wording for attributes 2019-09-15 04:55:18 -05:00			//~^ ERROR cannot find attribute `mutable_doc` in this scope
rustc: Add crate-level attribute lint 2013-11-25 09:22:40 -06:00
resolve: Use `feature(custom_attribute)` fallback only if the feature is enabled Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them. It also helps with unifying diagnostics for unresolved macros. 2019-07-11 17:00:20 -05:00			`#[dance] mod a {}`
resolve: Tweak "cannot find" wording for attributes 2019-09-15 04:55:18 -05:00			//~^ ERROR cannot find attribute `dance` in this scope
Add test for unknown attribute lint 2013-11-11 02:51:27 -06:00
resolve: Use `feature(custom_attribute)` fallback only if the feature is enabled Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them. It also helps with unifying diagnostics for unresolved macros. 2019-07-11 17:00:20 -05:00			`#[dance] fn main() {}`
resolve: Tweak "cannot find" wording for attributes 2019-09-15 04:55:18 -05:00			//~^ ERROR cannot find attribute `dance` in this scope