| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -808/+0 | |
| 2022-12-05 | Tweak "the following other types implement trait" | Esteban Küber | -20/+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-08-21 | Adjust messages, address some nits | Michael Goulet | -4/+4 | |
| 2022-08-21 | Rework point-at-arg | Michael Goulet | -18/+20 | |
| 2022-08-18 | Reword "Required because of the requirements on the impl of ..." | Andy Wang | -18/+18 | |
| 2022-07-16 | Use typeck_results to avoid duplicate ast_ty_to_ty call | Michael Goulet | -4/+4 | |
| 2022-07-07 | Shorten span for closures. | Camille GILLOT | -3/+3 | |
| 2022-06-28 | Note concrete type being coerced into object | Michael Goulet | -6/+6 | |
| 2022-06-19 | Greatly improve error reporting for futures and generators in ↵ | Joshua Nelson | -1/+5 | |
| `note_obligation_cause_code` Most futures don't go through this code path, because they're caught by `maybe_note_obligation_cause_for_async_await`. But all generators do, and `maybe_note` is imperfect and doesn't catch all futures. Improve the error message for those it misses. At some point, we may want to consider unifying this with the code for `maybe_note_async_await`, so that `async_await` notes all parent constraints, and `note_obligation` can point to yield points. But both functions are quite complicated, and it's not clear to me how to combine them; this seems like a good incremental improvement. | ||||
| 2022-06-03 | Fully stabilize NLL | Jack Huey | -183/+16 | |
| 2022-05-22 | Use revisions for NLL in various directories | Jack Huey | -39/+45 | |
| 2022-04-05 | Rollup merge of #95525 - ohno418:suggest-derivable-trait-E0277, ↵ | Dylan DPC | -0/+8 | |
| r=compiler-errors Suggest derivable trait on E0277 error Closes https://github.com/rust-lang/rust/issues/95099 . | ||||
| 2022-04-05 | Fix ui test for nll | ohno418 | -0/+4 | |
| 2022-04-05 | Suggest only when all fields impl the trait | ohno418 | -4/+0 | |
| 2022-04-05 | Suggest derivable trait on E0277 | ohno418 | -0/+8 | |
| 2022-04-04 | Remove hack, fix fmt and tests | Esteban Kuber | -0/+2 | |
| 2022-04-04 | Dedup logic and improve output for other types that impl trait | Esteban Kuber | -18/+18 | |
| 2022-04-04 | Fix list length | Esteban Kuber | -0/+8 | |
| 2022-04-04 | Fix #90970, doesn't address #87437 | Esteban Kuber | -0/+2 | |
| 2022-04-04 | Mention implementers of unsatisfied trait | Esteban Kuber | -2/+2 | |
| 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 | further update `fuzzy_match_tys` | lcnr | -12/+8 | |
| 2022-02-14 | fuzzify `fuzzy_match_tys` | lcnr | -8/+12 | |
| 2022-02-14 | Make `find_similar_impl_candidates` a little fuzzier. | Ben Reeves | -0/+8 | |
| 2021-09-26 | Remove box syntax from most places in src/test outside of the issues dir | est31 | -9/+9 | |
| 2021-09-16 | Point at call span that introduced obligation for the arg | Esteban Kuber | -3/+9 | |
| 2021-08-16 | Use note to point at bound introducing requirement | Esteban Küber | -75/+134 | |
| 2021-08-11 | Modify structured suggestion output | Esteban Küber | -8/+8 | |
| * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span | ||||
| 2021-07-31 | Point at unmet explicit lifetime obligation bound | Esteban Küber | -1/+5 | |
| 2021-04-07 | rebase and update tests | Esteban Küber | -6/+30 | |
| 2021-04-06 | Point at `impl` and type defs introducing requirements on E0277 | Esteban Küber | -9/+45 | |
| 2021-03-31 | give full path of constraint in suggest_constraining_type_param | hi-rustin | -16/+16 | |
| revert file bless with nll mode | ||||
| 2020-10-20 | review comments | Esteban Küber | -3/+3 | |
| 2020-10-20 | Tweak "object unsafe" errors | Esteban Küber | -14/+21 | |
| Fix #77598. | ||||
| 2020-09-28 | pretty.rs: Update Closure and Generator print | Aman Arora | -3/+3 | |
| Co-authored-by: Dhruv Jauhar <dhruvjhr@gmail.com> Co-authored-by: Logan Mosier <logmosier@gmail.com> | ||||
| 2020-09-02 | pretty: trim paths of unique symbols | Dan Aloni | -122/+122 | |
| 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-07-14 | Remove redundant explanatory `note` for type parameters | Esteban Küber | -4/+0 | |
| 2020-04-08 | Small tweaks to required bound span | Esteban Küber | -25/+25 | |
| 2020-03-29 | Tweak `suggest_constraining_type_param` | Esteban Küber | -40/+32 | |
| Some of the bound restriction structured suggestions were incorrect while others had subpar output. | ||||
| 2020-02-09 | Improve reporting errors and suggestions for trait bounds | Patryk Wychowaniec | -24/+40 | |
| 2020-02-02 | Wording changes to object unsafe trait errors | Esteban Küber | -3/+9 | |
| Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920 | ||||
| 2020-02-02 | Slight rewording of diagnostic message | Esteban Küber | -3/+3 | |
| 2020-02-02 | Tweak `Self: Sized` restriction diagnostic output | Esteban Küber | -4/+9 | |
| 2020-01-08 | Point at the def span of trait refs E0277 | Esteban Küber | -1/+3 | |
| 2019-12-30 | Add error code explanation for E0477 | Donough Liu | -2/+4 | |
| 2019-11-16 | Account for `rustc_on_unimplemented` | Esteban Küber | -1/+1 | |
| 2019-11-16 | Suggest borrowing when it would satisfy an unmet trait bound | Esteban Küber | -3/+3 | |
| When there are multiple implementors for the same trait that is present in an unmet binding, modify the E0277 error to refer to the parent obligation and verify whether borrowing the argument being passed in would satisfy the unmet bound. If it would, suggest it. | ||||
| 2019-10-23 | Auto merge of #57545 - bovinebuddha:object_safe_for_dispatch, r=nikomatsakis | bors | -6/+37 | |
| Object safe for dispatch cc #43561 | ||||
| 2019-10-22 | RFC 2027: "first draft" of implementation | Mathias Blikstad | -6/+37 | |
| These are a squashed series of commits. | ||||
| 2019-10-15 | Update NLL tests | Esteban Küber | -4/+12 | |
| 2019-10-15 | Use structured suggestion for restricting bounds | Esteban Küber | -4/+12 | |
| When a trait bound is not met and restricting a type parameter would make the restriction hold, use a structured suggestion pointing at an appropriate place (type param in param list or `where` clause). Account for opaque parameters where instead of suggesting extending the `where` clause, we suggest appending the new restriction: `fn foo(impl Trait + UnmetTrait)`. | ||||
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |