rust/src/test/ui/suggestions/attribute-typos.stderr

error[E0658]: attributes starting with `rustc` are reserved for use by the `rustc` compiler
  --> $DIR/attribute-typos.rs:7:3
   |
LL | #[rustc_err]
   |   ^^^^^^^^^
   |
   = note: for more information, see https://github.com/rust-lang/rust/issues/29642
   = help: add `#![feature(rustc_attrs)]` to the crate attributes to enable

error: cannot find attribute macro `rustc_err` in this scope
  --> $DIR/attribute-typos.rs:7:3
   |
LL | #[rustc_err]
   |   ^^^^^^^^^

error: cannot find attribute macro `tests` in this scope
  --> $DIR/attribute-typos.rs:4:3
   |
LL | #[tests]
   |   ^^^^^ help: try: `test`

error: cannot find attribute macro `deprcated` in this scope
  --> $DIR/attribute-typos.rs:1:3
   |
LL | #[deprcated]
   |   ^^^^^^^^^

error: aborting due to 4 previous errors

For more information about this error, try `rustc --explain E0658`.
Feature gate `rustc` attributes harder 2019-06-30 05:00:45 -05:00			error[E0658]: attributes starting with `rustc` are reserved for use by the `rustc` compiler
			`--> $DIR/attribute-typos.rs:7:3`
			`\|`
			`LL \| #[rustc_err]`
			`\| ^^^^^^^^^`
			`\|`
			`= note: for more information, see https://github.com/rust-lang/rust/issues/29642`
normalize use of backticks in compiler messages for libsyntax/feature_gate https://github.com/rust-lang/rust/issues/60532 2019-07-09 04:32:08 -05:00			= help: add `#![feature(rustc_attrs)]` to the crate attributes to enable
Feature gate `rustc` attributes harder 2019-06-30 05:00:45 -05: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			error: cannot find attribute macro `rustc_err` in this scope
Make sure `#[rustc_doc_only_macro]` and other rustc attributes are registered 2019-06-29 06:06:22 -05:00			`--> $DIR/attribute-typos.rs:7:3`
add typo suggestion to unknown attribute error 2019-01-25 13:29:47 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| #[rustc_err]`
add typo suggestion to unknown attribute error 2019-01-25 13:29:47 -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			error: cannot find attribute macro `tests` in this scope
Make sure `#[rustc_doc_only_macro]` and other rustc attributes are registered 2019-06-29 06:06:22 -05:00			`--> $DIR/attribute-typos.rs:4:3`
add typo suggestion to unknown attribute error 2019-01-25 13:29:47 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| #[tests]`
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			\| ^^^^^ help: try: `test`
add typo suggestion to unknown attribute error 2019-01-25 13:29:47 -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			error: cannot find attribute macro `deprcated` in this scope
add typo suggestion to unknown attribute error 2019-01-25 13:29:47 -06:00			`--> $DIR/attribute-typos.rs:1:3`
			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| #[deprcated]`
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			`\| ^^^^^^^^^`
add typo suggestion to unknown attribute error 2019-01-25 13:29:47 -06:00
Feature gate `rustc` attributes harder 2019-06-30 05:00:45 -05:00			`error: aborting due to 4 previous errors`
add typo suggestion to unknown attribute error 2019-01-25 13:29:47 -06:00
			For more information about this error, try `rustc --explain E0658`.