mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
df5c2cf9bc
rust/tests/ui/feature-gates/feature-gate-custom_attribute.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

81 lines
2.1 KiB
Plaintext
Raw Normal View History

resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:3:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:4:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(100)]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:5:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(1, 2, 3)]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:6:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr("hello")]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:7:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(name = "hello")]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:8:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(1, "hi", key = 12, true, false)]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:9:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(key = "hello", val = 10)]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:10:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(key("hello"), val(10))]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:11:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(enabled = true, disabled = false)]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:12:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(true)]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:13:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(pi = 3.14159)]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_attr` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:14:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_attr(b"hi")]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
resolve: Tweak "cannot find" wording for attributes
2019-09-15 04:55:18 -05:00
error: cannot find attribute `fake_doc` in this scope
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
--> $DIR/feature-gate-custom_attribute.rs:15:3
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | #[fake_doc(r"doc")]
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def`
2018-08-14 19:51:12 -05:00
| ^^^^^^^^
Migrate even more feature gate tests to ui We also rename some of the files to conform to the feature-gate-<feat_name>.rs pattern that is most common.
2017-12-06 03:18:03 -06:00
error: aborting due to 13 previous errors
Reference in New Issue Copy Permalink