os-rust/tests/ui/missing-trait-bounds/issue-35677.stderr

error[E0599]: the method `is_subset` exists for reference `&HashSet<T>`, but its trait bounds were not satisfied
  --> $DIR/issue-35677.rs:7:10
   |
LL |     this.is_subset(other)
   |          ^^^^^^^^^ method cannot be called on `&HashSet<T>` due to unsatisfied trait bounds
   |
   = note: the following trait bounds were not satisfied:
           `T: Eq`
           `T: PartialEq`
           which is required by `T: Eq`
           `T: Hash`
help: consider restricting the type parameters to satisfy the trait bounds
   |
LL | fn is_subset<T>(this: &HashSet<T>, other: &HashSet<T>) -> bool where T: Eq, T: Hash {
   |                                                                ++++++++++++++++++++

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0599`.
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 17:20:14 -04:00			error[E0599]: the method `is_subset` exists for reference `&HashSet<T>`, but its trait bounds were not satisfied
Suggest constraining `fn` type params when appropriate 2021-10-13 16:07:22 +00:00			`--> $DIR/issue-35677.rs:7:10`
Deduplicate unsatisfied trait bounds 2018-12-12 15:58:27 -08:00			`\|`
Relax some Hash bounds on HashMap<K, V, S> and HashSet<T, S> Notably, hash iterators don't require any trait bounds to be iterated. 2019-02-11 11:58:56 +01:00			`LL \| this.is_subset(other)`
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 17:20:14 -04:00			\| ^^^^^^^^^ method cannot be called on `&HashSet<T>` due to unsatisfied trait bounds
Deduplicate unsatisfied trait bounds 2018-12-12 15:58:27 -08: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 17:20:14 -04:00			`= note: the following trait bounds were not satisfied:`
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 10:40:56 +03:00			`T: Eq`
Elaborate unmet obligations in E0599 for more context 2023-01-12 19:53:01 +00:00			`T: PartialEq`
			which is required by `T: Eq`
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 10:40:56 +03:00			`T: Hash`
Suggest constraining `fn` type params when appropriate 2021-10-13 16:07:22 +00:00			`help: consider restricting the type parameters to satisfy the trait bounds`
			`\|`
Do not incorrectly suggest restricting implied bounds When we have already suggested bounds that imply the about to be suggested bound, skip them. 2023-01-13 20:50:34 +00:00			`LL \| fn is_subset<T>(this: &HashSet<T>, other: &HashSet<T>) -> bool where T: Eq, T: Hash {`
			`\| ++++++++++++++++++++`
Deduplicate unsatisfied trait bounds 2018-12-12 15:58:27 -08:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Deduplicate unsatisfied trait bounds 2018-12-12 15:58:27 -08:00
Do not abort compilation if expansion produces errors Fix a number of uncovered deficiencies in diagnostics 2018-12-16 20:23:27 +03:00			For more information about this error, try `rustc --explain E0599`.