mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
rust/tests/ui/rust-2018/edition-lint-nested-empty-paths.stderr

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

55 lines
2.8 KiB
Plaintext
Raw Normal View History

handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
error: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
Remove licenses
2018-12-25 08:56:47 -07:00
--> $DIR/edition-lint-nested-empty-paths.rs:17:5
handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
|
LL | use foo::{bar::{baz::{}}};
| ^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::foo::{bar::{baz::{}}}`
|
bless ui tests
2022-09-18 19:55:36 +04:00
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2018!
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
Normalise notes with the/is
2020-01-22 23:57:38 +00:00
note: the lint level is defined here
Remove licenses
2018-12-25 08:56:47 -07:00
--> $DIR/edition-lint-nested-empty-paths.rs:4:9
handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
|
Fix naming conventions for new lints
2018-05-19 01:13:53 +03:00
LL | #![deny(absolute_paths_not_starting_with_crate)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
error: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
resolve: Do not build expensive suggestions if they are not actually used Also remove a redundant parameter from `fn resolve_path(_with_ribs)`, `crate_lint: CrateLint` is a more detailed version of `record_used: bool` with `CrateLint::No` meaning `false` and anything else meaning `true`.
2022-03-23 22:47:19 +03:00
--> $DIR/edition-lint-nested-empty-paths.rs:21:5
handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
|
LL | use foo::{bar::{XX, baz::{}}};
| ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::foo::{bar::{XX, baz::{}}}`
|
Address PR feedback
2021-06-16 14:27:44 +02:00
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2018!
pick a reference issue for absolute-paths future incompatibility info It would be kind of embarrassing to ship with the "issue TBD" message!
2018-10-20 11:17:42 -07:00
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
error: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
resolve: Do not build expensive suggestions if they are not actually used Also remove a redundant parameter from `fn resolve_path(_with_ribs)`, `crate_lint: CrateLint` is a more detailed version of `record_used: bool` with `CrateLint::No` meaning `false` and anything else meaning `true`.
2022-03-23 22:47:19 +03:00
--> $DIR/edition-lint-nested-empty-paths.rs:21:5
Remove deduplication of early lints We already have a general mechanism for deduplicating reported lints, so there's no need to have an additional one for early lints specifically. This allows us to remove some `PartialEq` impls.
2022-01-23 17:05:48 -05:00
|
LL | use foo::{bar::{XX, baz::{}}};
| ^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::foo::{bar::{XX, baz::{}}}`
|
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2018!
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Remove deduplication of early lints We already have a general mechanism for deduplicating reported lints, so there's no need to have an additional one for early lints specifically. This allows us to remove some `PartialEq` impls.
2022-01-23 17:05:48 -05:00
error: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
resolve: Do not build expensive suggestions if they are not actually used Also remove a redundant parameter from `fn resolve_path(_with_ribs)`, `crate_lint: CrateLint` is a more detailed version of `record_used: bool` with `CrateLint::No` meaning `false` and anything else meaning `true`.
2022-03-23 22:47:19 +03:00
--> $DIR/edition-lint-nested-empty-paths.rs:27:5
Remove deduplication of early lints We already have a general mechanism for deduplicating reported lints, so there's no need to have an additional one for early lints specifically. This allows us to remove some `PartialEq` impls.
2022-01-23 17:05:48 -05:00
|
LL | use foo::{bar::{baz::{}, baz1::{}}};
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::foo::{bar::{baz::{}, baz1::{}}}`
|
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2018!
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
error: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
resolve: Do not build expensive suggestions if they are not actually used Also remove a redundant parameter from `fn resolve_path(_with_ribs)`, `crate_lint: CrateLint` is a more detailed version of `record_used: bool` with `CrateLint::No` meaning `false` and anything else meaning `true`.
2022-03-23 22:47:19 +03:00
--> $DIR/edition-lint-nested-empty-paths.rs:27:5
handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
|
LL | use foo::{bar::{baz::{}, baz1::{}}};
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::foo::{bar::{baz::{}, baz1::{}}}`
|
Address PR feedback
2021-06-16 14:27:44 +02:00
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2018!
pick a reference issue for absolute-paths future incompatibility info It would be kind of embarrassing to ship with the "issue TBD" message!
2018-10-20 11:17:42 -07:00
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
resolve: Do not build expensive suggestions if they are not actually used Also remove a redundant parameter from `fn resolve_path(_with_ribs)`, `crate_lint: CrateLint` is a more detailed version of `record_used: bool` with `CrateLint::No` meaning `false` and anything else meaning `true`.
2022-03-23 22:47:19 +03:00
error: aborting due to 5 previous errors
handle fully qualified paths properly when linting fixes #50970
2018-05-22 19:01:09 -04:00
Reference in New Issue Copy Permalink