nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-24 07:44:10 +00:00
Code Issues Packages Projects Releases Wiki Activity
8c01b85dba
rust/tests/ui/missing-trait-bounds/missing-trait-bounds-for-method-call.stderr

49 lines
1.8 KiB
Plaintext
Raw Normal View History

Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note.
2020-09-26 21:20:14 +00:00
error[E0599]: the method `foo` exists for reference `&Foo<T>`, but its trait bounds were not satisfied
Suggest constraining type parameters
2020-02-19 22:26:46 +00:00
--> $DIR/missing-trait-bounds-for-method-call.rs:14:14
|
LL | struct Foo<T> {
| ------------- doesn't satisfy `Foo<T>: Bar`
...
LL | self.foo();
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note.
2020-09-26 21:20:14 +00:00
| ^^^ method cannot be called on `&Foo<T>` due to unsatisfied trait bounds
Suggest constraining type parameters
2020-02-19 22:26:46 +00:00
|
Tweak output
2023-01-11 04:11:06 +00:00
note: the following trait bounds were not satisfied:
`T: Bar`
`T: Default`
Properly track `ImplObligation`s Instead of probing for all possible impls that could have caused an `ImplObligation`, keep track of its `DefId` and obligation spans for accurate error reporting. Follow up to #89580. Addresses #89418. Remove some unnecessary clones. Tweak output for auto trait impl obligations.
2021-10-13 13:58:41 +00:00
--> $DIR/missing-trait-bounds-for-method-call.rs:10:9
|
LL | impl<T: Default + Bar> Bar for Foo<T> {}
Tweak output
2023-01-11 04:11:06 +00:00
| ^^^^^^^ ^^^ --- ------
| | |
| | unsatisfied trait bound introduced here
Properly track `ImplObligation`s Instead of probing for all possible impls that could have caused an `ImplObligation`, keep track of its `DefId` and obligation spans for accurate error reporting. Follow up to #89580. Addresses #89418. Remove some unnecessary clones. Tweak output for auto trait impl obligations.
2021-10-13 13:58:41 +00:00
| unsatisfied trait bound introduced here
Reword message
2020-02-25 20:08:22 +00:00
help: consider restricting the type parameters to satisfy the trait bounds
Suggest constraining type parameters
2020-02-19 22:26:46 +00: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 07:40:56 +00:00
LL | struct Foo<T> where T: Bar, T: Default {
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
| ++++++++++++++++++++++++
Suggest constraining type parameters
2020-02-19 22:26:46 +00:00
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note.
2020-09-26 21:20:14 +00:00
error[E0599]: the method `foo` exists for reference `&Fin<T>`, but its trait bounds were not satisfied
Suggest constraining type parameters
2020-02-19 22:26:46 +00:00
--> $DIR/missing-trait-bounds-for-method-call.rs:27:14
|
LL | struct Fin<T> where T: Bar {
Shorten def_span for more items.
2022-02-13 15:27:59 +00:00
| ------------- doesn't satisfy `Fin<T>: Bar`
Suggest constraining type parameters
2020-02-19 22:26:46 +00:00
...
LL | self.foo();
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note.
2020-09-26 21:20:14 +00:00
| ^^^ method cannot be called on `&Fin<T>` due to unsatisfied trait bounds
Suggest constraining type parameters
2020-02-19 22:26:46 +00:00
|
Properly track `ImplObligation`s Instead of probing for all possible impls that could have caused an `ImplObligation`, keep track of its `DefId` and obligation spans for accurate error reporting. Follow up to #89580. Addresses #89418. Remove some unnecessary clones. Tweak output for auto trait impl obligations.
2021-10-13 13:58:41 +00:00
note: trait bound `T: Default` was not satisfied
--> $DIR/missing-trait-bounds-for-method-call.rs:23:9
|
LL | impl<T: Default + Bar> Bar for Fin<T> {}
| ^^^^^^^ --- ------
| |
| unsatisfied trait bound introduced here
Reword message
2020-02-25 20:08:22 +00:00
help: consider restricting the type parameter to satisfy the trait bound
Suggest constraining type parameters
2020-02-19 22:26:46 +00: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 07:40:56 +00:00
LL | struct Fin<T> where T: Bar, T: Default {
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
| ++++++++++++
Suggest constraining type parameters
2020-02-19 22:26:46 +00:00
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0599`.
Reference in New Issue Copy Permalink