rust/tests/ui/missing-trait-bounds/issue-35677.rs

// run-rustfix
#![allow(dead_code)]
use std::collections::HashSet;
use std::hash::Hash;

fn is_subset<T>(this: &HashSet<T>, other: &HashSet<T>) -> bool {
    this.is_subset(other)
    //~^ ERROR the method
}

fn main() {}
Suggest constraining `fn` type params when appropriate 2021-10-13 16:07:22 +00:00			`// run-rustfix`
			`#![allow(dead_code)]`
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			`use std::collections::HashSet;`
Suggest constraining `fn` type params when appropriate 2021-10-13 16:07:22 +00:00			`use std::hash::Hash;`
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
			`fn is_subset<T>(this: &HashSet<T>, other: &HashSet<T>) -> bool {`
			`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			`//~^ ERROR the method`
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
			`fn main() {}`