nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-12-03 04:04:06 +00:00
Code Issues Packages Projects Releases Wiki Activity
a99209738e
rust/tests/ui/rust-2018/edition-lint-paths.stderr

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

89 lines
4.3 KiB
Plaintext
Raw Normal View History

rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00:00
error: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition
Remove licenses
2018-12-25 15:56:47 +00:00
--> $DIR/edition-lint-paths.rs:12:9
Add test
2018-04-20 23:30:14 +00:00
|
Address PR feedback
2021-06-16 12:27:44 +00:00
LL | use bar::Bar;
| ^^^^^^^^ help: use `crate`: `crate::bar::Bar`
Add test
2018-04-20 23:30:14 +00:00
|
bless ui tests
2022-09-18 15:55:36 +00: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 15:56:47 +00:00
--> $DIR/edition-lint-paths.rs:5:9
Add test
2018-04-20 23:30:14 +00:00
|
Fix naming conventions for new lints
2018-05-18 22:13:53 +00:00
LL | #![deny(absolute_paths_not_starting_with_crate)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Add test
2018-04-20 23:30:14 +00:00
rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00: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 19:47:19 +00:00
--> $DIR/edition-lint-paths.rs:19:9
rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00:00
|
LL | use bar;
| ^^^ help: use `crate`: `crate::bar`
|
Address PR feedback
2021-06-16 12:27:44 +00: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 18:17:42 +00:00
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00: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 19:47:19 +00:00
--> $DIR/edition-lint-paths.rs:25:9
rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00:00
|
Address PR feedback
2021-06-16 12:27:44 +00:00
LL | use {main, Bar as SomethingElse};
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::{main, Bar as SomethingElse}`
rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00:00
|
Address PR feedback
2021-06-16 12:27:44 +00: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 18:17:42 +00:00
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00: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 19:47:19 +00:00
--> $DIR/edition-lint-paths.rs:25:9
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 22:05:48 +00:00
|
LL | use {main, Bar as SomethingElse};
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::{main, Bar as SomethingElse}`
|
= 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 19:47:19 +00:00
--> $DIR/edition-lint-paths.rs:25:9
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 22:05:48 +00:00
|
LL | use {main, Bar as SomethingElse};
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `crate`: `crate::{main, Bar as SomethingElse}`
|
= 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 19:47:19 +00:00
--> $DIR/edition-lint-paths.rs:40: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 22:05:48 +00:00
|
LL | use bar::Bar;
| ^^^^^^^^ help: use `crate`: `crate::bar::Bar`
|
= 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 19:47:19 +00:00
--> $DIR/edition-lint-paths.rs:52:9
rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00:00
|
LL | use *;
| ^ help: use `crate`: `crate::*`
|
Address PR feedback
2021-06-16 12:27:44 +00: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 18:17:42 +00:00
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
rustc: Fix `crate` lint for single-item paths This commit fixes recommending the `crate` prefix when migrating to 2018 for paths that look like `use foo;` or `use {bar, baz}` Closes #50660
2018-05-11 17:02:17 +00: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 19:47:19 +00:00
--> $DIR/edition-lint-paths.rs:57:6
add new test and add an existing scenario I didn't see covered
2018-05-22 15:45:44 +00:00
|
Address PR feedback
2021-06-16 12:27:44 +00:00
LL | impl ::foo::SomeTrait for u32 {}
add new test and add an existing scenario I didn't see covered
2018-05-22 15:45:44 +00:00
| ^^^^^^^^^^^^^^^^ help: use `crate`: `crate::foo::SomeTrait`
|
Address PR feedback
2021-06-16 12:27:44 +00: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 18:17:42 +00:00
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
add new test and add an existing scenario I didn't see covered
2018-05-22 15:45:44 +00: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 19:47:19 +00:00
--> $DIR/edition-lint-paths.rs:62:13
Add test
2018-04-20 23:30:14 +00:00
|
LL | let x = ::bar::Bar;
| ^^^^^^^^^^ help: use `crate`: `crate::bar::Bar`
|
Address PR feedback
2021-06-16 12:27:44 +00: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 18:17:42 +00:00
= note: for more information, see issue #53130 <https://github.com/rust-lang/rust/issues/53130>
Add test
2018-04-20 23:30:14 +00: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 19:47:19 +00:00
error: aborting due to 9 previous errors
Add test
2018-04-20 23:30:14 +00:00
Reference in New Issue Copy Permalink