nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-27 09:14:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
75655a9246
rust/tests/ui/privacy/privacy-ns1.stderr

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

68 lines
1.6 KiB
Plaintext
Raw Normal View History

Point at local similarly named element and tweak references to variants Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-15 00:20:50 +00:00
error[E0423]: expected function, tuple struct or tuple variant, found trait `Bar`
Remove licenses
2018-12-25 15:56:47 +00:00
--> $DIR/privacy-ns1.rs:20:5
Moved compile-fail tests to ui tests.
2018-08-08 12:28:26 +00:00
|
Point at local similarly named element and tweak references to variants Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-15 00:20:50 +00:00
LL | pub struct Baz;
| --------------- similarly named unit struct `Baz` defined here
...
Update tests
2019-03-09 12:03:44 +00:00
LL | Bar();
clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion.
2019-01-09 19:11:00 +00:00
| ^^^
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-24 05:20:58 +00:00
|
clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion.
2019-01-09 19:11:00 +00:00
help: a unit struct with a similar name exists
|
Update tests
2019-03-09 12:03:44 +00:00
LL | Baz();
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| ~~~
Prefer accessible paths in 'use' suggestions This fixes an issue with the following sample: mod foo { mod inaccessible { pub struct X; } pub mod avail { pub struct X; } } fn main() { X; } Instead of suggesting both `use crate::foo::inaccessible::X;` and `use crate::foo::avail::X;`, it should only suggest the latter. It is done by trimming the list of suggestions from inaccessible paths if accessible paths are present. Visibility is checked with `is_accessible_from` now instead of being hard-coded. - Some tests fixes are trivial, and others require a bit more explaining, here are my comments: src/test/ui/issues/issue-35675.stderr: Only needs to make the enum public to have the suggestion make sense. src/test/ui/issues/issue-42944.stderr: Importing the tuple struct won't help because its constructor is not visible, so the attempted constructor does not work. In that case, it's better not to suggest it. The case where the constructor is public is covered in `issue-26545.rs`.
2020-06-13 17:58:46 +00:00
help: consider importing this function instead
Moved compile-fail tests to ui tests.
2018-08-08 12:28:26 +00:00
|
LL | use foo2::Bar;
|
Point at local similarly named element and tweak references to variants Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-15 00:20:50 +00:00
error[E0425]: cannot find function, tuple struct or tuple variant `Bar` in this scope
test: Update tests with fallout of changes The error messages of the two tests effected degraded in quality. The errors no longer suggest types in other modules as they now assume that the arguments are const args, not type args.
2019-11-18 19:57:46 +00:00
--> $DIR/privacy-ns1.rs:51:5
Moved compile-fail tests to ui tests.
2018-08-08 12:28:26 +00:00
|
Point at local similarly named element and tweak references to variants Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-15 00:20:50 +00:00
LL | pub struct Baz;
| --------------- similarly named unit struct `Baz` defined here
...
Update tests
2019-03-09 12:03:44 +00:00
LL | Bar();
clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion.
2019-01-09 19:11:00 +00:00
| ^^^
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-24 05:20:58 +00:00
|
clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion.
2019-01-09 19:11:00 +00:00
help: a unit struct with a similar name exists
|
Update tests
2019-03-09 12:03:44 +00:00
LL | Baz();
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| ~~~
Prefer accessible paths in 'use' suggestions This fixes an issue with the following sample: mod foo { mod inaccessible { pub struct X; } pub mod avail { pub struct X; } } fn main() { X; } Instead of suggesting both `use crate::foo::inaccessible::X;` and `use crate::foo::avail::X;`, it should only suggest the latter. It is done by trimming the list of suggestions from inaccessible paths if accessible paths are present. Visibility is checked with `is_accessible_from` now instead of being hard-coded. - Some tests fixes are trivial, and others require a bit more explaining, here are my comments: src/test/ui/issues/issue-35675.stderr: Only needs to make the enum public to have the suggestion make sense. src/test/ui/issues/issue-42944.stderr: Importing the tuple struct won't help because its constructor is not visible, so the attempted constructor does not work. In that case, it's better not to suggest it. The case where the constructor is public is covered in `issue-26545.rs`.
2020-06-13 17:58:46 +00:00
help: consider importing this function
Moved compile-fail tests to ui tests.
2018-08-08 12:28:26 +00:00
|
LL | use foo2::Bar;
|
error[E0412]: cannot find type `Bar` in this scope
test: Update tests with fallout of changes The error messages of the two tests effected degraded in quality. The errors no longer suggest types in other modules as they now assume that the arguments are const args, not type args.
2019-11-18 19:57:46 +00:00
--> $DIR/privacy-ns1.rs:52:17
Moved compile-fail tests to ui tests.
2018-08-08 12:28:26 +00:00
|
Point at local similarly named element and tweak references to variants Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-15 00:20:50 +00:00
LL | pub struct Baz;
| --------------- similarly named struct `Baz` defined here
...
Update tests
2019-03-09 12:03:44 +00:00
LL | let _x: Box<Bar>;
clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion.
2019-01-09 19:11:00 +00:00
| ^^^
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-24 05:20:58 +00:00
|
clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion.
2019-01-09 19:11:00 +00:00
help: a struct with a similar name exists
|
Update tests
2019-03-09 12:03:44 +00:00
LL | let _x: Box<Baz>;
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| ~~~
Prefer accessible paths in 'use' suggestions This fixes an issue with the following sample: mod foo { mod inaccessible { pub struct X; } pub mod avail { pub struct X; } } fn main() { X; } Instead of suggesting both `use crate::foo::inaccessible::X;` and `use crate::foo::avail::X;`, it should only suggest the latter. It is done by trimming the list of suggestions from inaccessible paths if accessible paths are present. Visibility is checked with `is_accessible_from` now instead of being hard-coded. - Some tests fixes are trivial, and others require a bit more explaining, here are my comments: src/test/ui/issues/issue-35675.stderr: Only needs to make the enum public to have the suggestion make sense. src/test/ui/issues/issue-42944.stderr: Importing the tuple struct won't help because its constructor is not visible, so the attempted constructor does not work. In that case, it's better not to suggest it. The case where the constructor is public is covered in `issue-26545.rs`.
2020-06-13 17:58:46 +00:00
help: consider importing this trait
Moved compile-fail tests to ui tests.
2018-08-08 12:28:26 +00:00
|
LL | use foo1::Bar;
|
improve error message for const ty param mismatch
2020-11-13 19:23:37 +00:00
error[E0747]: constant provided when a type was expected
test: Update tests with fallout of changes The error messages of the two tests effected degraded in quality. The errors no longer suggest types in other modules as they now assume that the arguments are const args, not type args.
2019-11-18 19:57:46 +00:00
--> $DIR/privacy-ns1.rs:35:17
|
LL | let _x: Box<Bar>;
improve error message for const ty param mismatch
2020-11-13 19:23:37 +00:00
| ^^^
Improve diagnostics for function passed when a type was expected.
2021-04-24 14:25:36 +00:00
|
= help: `Bar` is a function item, not a type
= help: function item types cannot be named directly
test: Update tests with fallout of changes The error messages of the two tests effected degraded in quality. The errors no longer suggest types in other modules as they now assume that the arguments are const args, not type args.
2019-11-18 19:57:46 +00:00
improve error message for const ty param mismatch
2020-11-13 19:23:37 +00:00
error: aborting due to 4 previous errors
Moved compile-fail tests to ui tests.
2018-08-08 12:28:26 +00:00
improve error message for const ty param mismatch
2020-11-13 19:23:37 +00:00
Some errors have detailed explanations: E0412, E0423, E0425, E0747.
For more information about an error, try `rustc --explain E0412`.
Reference in New Issue Copy Permalink