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

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

44 lines
2.1 KiB
Plaintext
Raw Normal View History

add new test and add an existing scenario I didn't see covered
2018-05-22 10:45:44 -05:00
error: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/edition-lint-nested-paths.rs:6:5
add new test and add an existing scenario I didn't see covered
2018-05-22 10:45:44 -05:00
|
LL | use foo::{a, b};
| ^^^^^^^^^^^ help: use `crate`: `crate::foo::{a, b}`
|
bless ui tests
2022-09-18 10:55:36 -05: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 17:57:38 -06:00
note: the lint level is defined here
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/edition-lint-nested-paths.rs:4:9
add new test and add an existing scenario I didn't see covered
2018-05-22 10:45:44 -05:00
|
Fix naming conventions for new lints
2018-05-18 17:13:53 -05:00
LL | #![deny(absolute_paths_not_starting_with_crate)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
add new test and add an existing scenario I didn't see covered
2018-05-22 10:45:44 -05:00
rustc: Fix another double-lint issue with `crate::` This commit fixes another issue in the `absolute_path_not_starting_with_crate` lint where it warns twice about an import which may contain `self`. It turns out there were a few more locations that needed updating to use `root_id` and `root_span` introduced in #50970 and after that it looks to work like a charm! Closes #50978
2018-05-22 17:34:30 -05:00
error: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
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 16:05:48 -06:00
--> $DIR/edition-lint-nested-paths.rs:6:5
|
LL | use foo::{a, b};
| ^^^^^^^^^^^ help: use `crate`: `crate::foo::{a, b}`
|
= 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 14:47:19 -05:00
--> $DIR/edition-lint-nested-paths.rs:23:13
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 16:05:48 -06:00
|
LL | use foo::{self as x, c};
| ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::foo::{self as x, c}`
|
= 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 14:47:19 -05:00
--> $DIR/edition-lint-nested-paths.rs:23:13
rustc: Fix another double-lint issue with `crate::` This commit fixes another issue in the `absolute_path_not_starting_with_crate` lint where it warns twice about an import which may contain `self`. It turns out there were a few more locations that needed updating to use `root_id` and `root_span` introduced in #50970 and after that it looks to work like a charm! Closes #50978
2018-05-22 17:34:30 -05:00
|
LL | use foo::{self as x, c};
| ^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::foo::{self as x, c}`
|
Address PR feedback
2021-06-16 07:27:44 -05: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 13:17:42 -05:00
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
rustc: Fix another double-lint issue with `crate::` This commit fixes another issue in the `absolute_path_not_starting_with_crate` lint where it warns twice about an import which may contain `self`. It turns out there were a few more locations that needed updating to use `root_id` and `root_span` introduced in #50970 and after that it looks to work like a charm! Closes #50978
2018-05-22 17:34:30 -05: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 14:47:19 -05:00
error: aborting due to 4 previous errors
add new test and add an existing scenario I didn't see covered
2018-05-22 10:45:44 -05:00
Reference in New Issue Copy Permalink