| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -18/+0 | |
| 2022-09-26 | address review | b-naber | -3/+3 | |
| 2021-01-26 | Avoid describing a method as 'not found' when bounds are unsatisfied | Aaron Hill | -3/+3 | |
| 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-06-22 | remove snapshot calls from "match" operations during select | Niko Matsakis | -0/+2 | |
| Motivation: - we want to use leak-check sparingly, first off - these calls were essentially the same as doing the check during subtyping | ||||
| 2020-06-22 | Revert "modify leak-check to track only outgoing edges from placeholders" | Niko Matsakis | -28/+11 | |
| This reverts commit 2e01db4b396a1e161f7a73933fff34bc9421dba0. | ||||
| 2020-06-22 | modify leak-check to track only outgoing edges from placeholders | Niko Matsakis | -11/+28 | |
| Also, update the affected tests. This seems strictly better but it is actually more permissive than I initially intended. In particular it accepts this ``` forall<'a, 'b> { exists<'intersection> { 'a: 'intersection, 'b: 'intersection, } } ``` and I'm not sure I want to accept that. It implies that we have a `'empty` in the new universe intoduced by the `forall`. | ||||
| 2020-02-28 | keep predicate order and tweak output | Esteban Küber | -3/+5 | |
| 2020-02-28 | Tweak wording | Esteban Küber | -1/+1 | |
| 2020-02-28 | Mention the full path of the implementing trait | Esteban Küber | -1/+1 | |
| 2020-02-28 | On single local candidate, use span label | Esteban Küber | -2/+3 | |
| 2020-01-08 | Unify output of "variant not found" errors | Esteban Küber | -1/+1 | |
| 2019-03-23 | Tweak spans for E0599 | Esteban Küber | -3/+1 | |
| 2019-03-11 | Update tests | Vadim Petrochenkov | -1/+1 | |
| 2019-02-21 | update test files to reflect new output | Niko Matsakis | -6/+10 | |
| One surprise: old-lub-glb-object.rs, may indicate a bug | ||||
| 2019-01-28 | Refer to synthetically named lifetimes as "some specific lifetime" rather ↵ | Rémy Rakic | -1/+1 | |
| than "the specific lifetime" | ||||
| 2019-01-27 | identify when implemented for "some specific lifetime" | Niko Matsakis | -0/+11 | |
