rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2022-04-04	Refer to the TraitRef::identity in the message to be clearer	Esteban Kuber	-2/+2

2022-04-04	Dedup logic and improve output for other types that impl trait	Esteban Kuber	-10/+10

2022-04-04	Fix list length	Esteban Kuber	-0/+8

2022-04-04	Mention implementers of unsatisfied trait	Esteban Kuber	-0/+12
	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 `?`.
2022-02-14	suggest using raw string literals when invalid escapes appear	Erin Petra Sofiya Moon	-0/+8
	i'd guess about 70% of "bad escape" cases occur when someone meant to use a raw string literal because they're passing it directly to Regex::new(). this emits an advisory (Applicability::MaybeIncorrect) help: suggestion to the user that they use an r"" string, on top of the normal notes about looking at the string literal documentation/spec.
2021-11-25	Move some tests to more reasonable directories	Caio	-0/+648