mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a733082be9
rust/tests/ui/traits/bound/same-crate-name.stderr

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

76 lines
3.2 KiB
Plaintext
Raw Normal View History

pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error[E0277]: the trait bound `Foo: main::a::Bar` is not satisfied
Organize trait test files
2021-02-08 16:15:45 -06:00
--> $DIR/same-crate-name.rs:31:20
Add version mismatch help message for unimplemented trait Issue #22750 The error reporting for E0277 (the trait `X` is not implemented for `Foo`) now checks whether `Foo` implements a trait with the same path as `X`, which probably means that the programmer wanted to actually use only one version of the trait `X` instead of the two.
2019-11-03 16:06:48 -06:00
|
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
LL | a::try_foo(foo);
Point at call span that introduced obligation for the arg
2021-09-07 06:30:53 -05:00
| ---------- ^^^ the trait `main::a::Bar` is not implemented for `Foo`
| |
| required by a bound introduced by this call
Remove trailing whitespace from error messages
2021-06-10 06:52:00 -05:00
|
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
help: trait impl with same name found
Add version mismatch help message for unimplemented trait Issue #22750 The error reporting for E0277 (the trait `X` is not implemented for `Foo`) now checks whether `Foo` implements a trait with the same path as `X`, which probably means that the programmer wanted to actually use only one version of the trait `X` instead of the two.
2019-11-03 16:06:48 -06:00
--> $DIR/auxiliary/crate_a2.rs:5:1
|
LL | impl Bar for Foo {}
Shorten def_span for more items.
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^
Diagnostics should start lowercase
2020-01-10 08:13:05 -06:00
= note: perhaps two different versions of crate `crate_a2` are being used?
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that *do* implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 | LL | impl Baz<f32> for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz<U: ?Sized> where U: Foo { } | ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`.
2021-12-13 14:56:40 -06:00
= help: the trait `main::a::Bar` is implemented for `ImplementsTraitForUsize<usize>`
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `try_foo`
--> $DIR/auxiliary/crate_a1.rs:3:24
|
LL | pub fn try_foo(x: impl Bar) {}
| ^^^ required by this bound in `try_foo`
Add version mismatch help message for unimplemented trait Issue #22750 The error reporting for E0277 (the trait `X` is not implemented for `Foo`) now checks whether `Foo` implements a trait with the same path as `X`, which probably means that the programmer wanted to actually use only one version of the trait `X` instead of the two.
2019-11-03 16:06:48 -06:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error[E0277]: the trait bound `DoesNotImplementTrait: main::a::Bar` is not satisfied
Organize trait test files
2021-02-08 16:15:45 -06:00
--> $DIR/same-crate-name.rs:38:20
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
|
LL | a::try_foo(implements_no_traits);
Point at call span that introduced obligation for the arg
2021-09-07 06:30:53 -05:00
| ---------- ^^^^^^^^^^^^^^^^^^^^ the trait `main::a::Bar` is not implemented for `DoesNotImplementTrait`
| |
| required by a bound introduced by this call
Remove trailing whitespace from error messages
2021-06-10 06:52:00 -05:00
|
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that *do* implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 | LL | impl Baz<f32> for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz<U: ?Sized> where U: Foo { } | ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`.
2021-12-13 14:56:40 -06:00
= help: the trait `main::a::Bar` is implemented for `ImplementsTraitForUsize<usize>`
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `try_foo`
--> $DIR/auxiliary/crate_a1.rs:3:24
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
|
LL | pub fn try_foo(x: impl Bar) {}
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
| ^^^ required by this bound in `try_foo`
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error[E0277]: the trait bound `ImplementsWrongTraitConditionally<isize>: main::a::Bar` is not satisfied
Organize trait test files
2021-02-08 16:15:45 -06:00
--> $DIR/same-crate-name.rs:45:20
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
|
LL | a::try_foo(other_variant_implements_mismatched_trait);
Point at call span that introduced obligation for the arg
2021-09-07 06:30:53 -05:00
| ---------- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `main::a::Bar` is not implemented for `ImplementsWrongTraitConditionally<isize>`
| |
| required by a bound introduced by this call
Remove trailing whitespace from error messages
2021-06-10 06:52:00 -05:00
|
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
help: trait impl with same name found
--> $DIR/auxiliary/crate_a2.rs:13:1
|
LL | impl Bar for ImplementsWrongTraitConditionally<isize> {}
Shorten def_span for more items.
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Diagnostics should start lowercase
2020-01-10 08:13:05 -06:00
= note: perhaps two different versions of crate `crate_a2` are being used?
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that *do* implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 | LL | impl Baz<f32> for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz<U: ?Sized> where U: Foo { } | ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`.
2021-12-13 14:56:40 -06:00
= help: the trait `main::a::Bar` is implemented for `ImplementsTraitForUsize<usize>`
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `try_foo`
--> $DIR/auxiliary/crate_a1.rs:3:24
|
LL | pub fn try_foo(x: impl Bar) {}
| ^^^ required by this bound in `try_foo`
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error[E0277]: the trait bound `ImplementsTraitForUsize<isize>: main::a::Bar` is not satisfied
Organize trait test files
2021-02-08 16:15:45 -06:00
--> $DIR/same-crate-name.rs:51:20
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
|
LL | a::try_foo(other_variant_implements_correct_trait);
Point at call span that introduced obligation for the arg
2021-09-07 06:30:53 -05:00
| ---------- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `main::a::Bar` is not implemented for `ImplementsTraitForUsize<isize>`
| |
| required by a bound introduced by this call
Remove trailing whitespace from error messages
2021-06-10 06:52:00 -05:00
|
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that *do* implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 | LL | impl Baz<f32> for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz<U: ?Sized> where U: Foo { } | ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`.
2021-12-13 14:56:40 -06:00
= help: the trait `main::a::Bar` is implemented for `ImplementsTraitForUsize<usize>`
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `try_foo`
--> $DIR/auxiliary/crate_a1.rs:3:24
|
LL | pub fn try_foo(x: impl Bar) {}
| ^^^ required by this bound in `try_foo`
fixup! Add negative tests where the diagnostic message would be wrong
2019-11-24 06:01:13 -06:00
error: aborting due to 4 previous errors
Add version mismatch help message for unimplemented trait Issue #22750 The error reporting for E0277 (the trait `X` is not implemented for `Foo`) now checks whether `Foo` implements a trait with the same path as `X`, which probably means that the programmer wanted to actually use only one version of the trait `X` instead of the two.
2019-11-03 16:06:48 -06:00
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink