| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -592/+0 | |
| 2022-12-05 | Tweak "the following other types implement trait" | Esteban Küber | -9/+2 | |
| When *any* of the suggested impls is an exact match, *only* show the exact matches. This is particularly relevant for integer types. fix fmt | ||||
| 2022-10-09 | From<Alignment> for usize & NonZeroUsize | Scott McMurray | -1/+1 | |
| 2022-09-04 | Use head span for rustc_on_unimplemented's enclosing_scope attr | Michael Goulet | -120/+78 | |
| 2022-08-18 | Reword "Required because of the requirements on the impl of ..." | Andy Wang | -1/+1 | |
| 2022-04-30 | Bless the UI tests | Scott McMurray | -7/+21 | |
| 2022-04-30 | Add `do yeet` expressions to allow experimentation in nightly | Scott McMurray | -0/+22 | |
| Using an obviously-placeholder syntax. An RFC would still be needed before this could have any chance at stabilization, and it might be removed at any point. But I'd really like to have it in nightly at least to ensure it works well with try_trait_v2, especially as we refactor the traits. | ||||
| 2022-04-04 | Refer to the TraitRef::identity in the message to be clearer | Esteban Kuber | -1/+1 | |
| 2022-04-04 | Dedup logic and improve output for other types that impl trait | Esteban Kuber | -3/+3 | |
| 2022-04-04 | Fix list length | Esteban Kuber | -0/+4 | |
| 2022-04-04 | Mention implementers of unsatisfied trait | Esteban Kuber | -1/+11 | |
| 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-03-03 | Cleanup feature gates. | Camille GILLOT | -5/+3 | |
| 2022-02-14 | further update `fuzzy_match_tys` | lcnr | -3/+3 | |
| 2022-02-14 | Make `find_similar_impl_candidates` a little fuzzier. | Ben Reeves | -0/+3 | |
| 2021-11-20 | Do not mention associated items when they introduce an obligation | Esteban Kuber | -100/+0 | |
| 2021-08-16 | Use note to point at bound introducing requirement | Esteban Küber | -2/+5 | |
| 2021-07-19 | Various diagnostics clean ups/tweaks | Esteban Küber | -20/+100 | |
| * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition | ||||
| 2021-05-23 | Extend rustc_on_implemented to improve a ?-on-ControlFlow error message | Scott McMurray | -13/+11 | |
| 2021-05-06 | Better rustc_on_unimplemented, and UI test fixes | Scott McMurray | -0/+609 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |