| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-04-18 | hide `--explain` hint if error has no extended info | Andy Russell | -2/+2 | |
| 2019-04-09 | improve unknown enum variant errors | Andy Russell | -1/+1 | |
| 2019-03-11 | Update tests | Vadim Petrochenkov | -13/+13 | |
| 2019-03-02 | Suggest removal of `&` when borrowing macro and appropriate | Esteban Küber | -1/+4 | |
| Fix #58815. | ||||
| 2019-01-20 | Use structured suggestion in stead of notes | Esteban Küber | -3/+1 | |
| 2019-01-12 | Reword label as per review comment | Esteban Küber | -1/+1 | |
| 2019-01-12 | Point at the match discriminant when arm pattern has a type mismatch | Esteban Küber | -0/+2 | |
| 2018-12-30 | Tweak E0308 error for clarity | Esteban Küber | -5/+5 | |
| 2018-12-30 | Point at function name span | Esteban Küber | -5/+15 | |
| 2018-12-30 | Point at the return type span on type mismatch due to missing return | Esteban Küber | -44/+30 | |
| Do not point at the entire block span on fn return type mismatches caused by missing return. | ||||
| 2018-12-25 | Remove licenses | Mark Rousskov | -138/+18 | |
| 2018-12-24 | make non_camel_case_types an early lint | Andy Russell | -2/+2 | |
| 2018-11-10 | in which the E0618 "expected function" diagnostic gets a makeover | Zack M. Davis | -2/+10 | |
| Now the main span focuses on the erroneous not-a-function callee, while showing the entire call expression is relegated to a secondary span. In the case where the erroneous callee is itself a call, we point out the definition, and, if the call expression spans multiple lines, tentatively suggest a semicolon (because we suspect that the "outer" call is actually supposed to be a tuple). The new `bug!` assertion is, in fact, safe (`confirm_builtin_call` is only called by `check_call`, which is only called with a first arg of kind `ExprKind::Call` in `check_expr_kind`). Resolves #51055. | ||||
| 2018-10-23 | fix typos in various places | Matthias Krüger | -1/+1 | |
| 2018-03-14 | update tests | Guillaume Gomez | -14/+14 | |
| 2018-02-26 | Update UI tests | Vadim Petrochenkov | -4/+4 | |
| 2018-02-26 | Update UI tests | Vadim Petrochenkov | -40/+40 | |
| 2018-02-25 | Update ui tests | Guillaume Gomez | -0/+14 | |
| 2018-01-15 | Further tweaks to the output | Esteban Küber | -1/+1 | |
| - Properly address Variant Ctors - Show signature if span of trait method without `self` is not available | ||||
| 2017-12-14 | Remove NOTE/HELP annotations from UI tests | Vadim Petrochenkov | -10/+10 | |
| 2017-11-24 | Merge cfail and ui tests into ui tests | Oliver Schneider | -6/+5 | |
| 2017-11-18 | move the signature into the closure type | Niko Matsakis | -12/+1 | |
| 2017-09-21 | Add suggestions for misspelled method names | Thomas Jespersen | -0/+2 | |
| Use the syntax::util::lev_distance module to provide suggestions when a named method cannot be found. Part of #30197 | ||||
| 2017-08-09 | Readd backticks around () | Esteban Küber | -4/+4 | |
| 2017-08-08 | Only refer to return type when it matches | Esteban Küber | -4/+4 | |
| 2017-07-25 | Point at return type always when type mismatch against it | Esteban Küber | -0/+9 | |
| Before this, the diagnostic errors would only point at the return type when changing it would be a possible solution to a type error. Add a label to the return type without a suggestion to change in order to make the source of the expected type obvious. Follow up to #42850, fixes #25133, fixes #41897. | ||||
| 2017-07-21 | Adjust new suggestions to the suggestion guidelines | Oliver Schneider | -2/+2 | |
| 2017-07-06 | Only underline suggestion if it is not the only code being shown | Esteban Küber | -2/+6 | |
| 2017-07-02 | report the total number of errors on compilation failure | Ariel Ben-Yehuda | -12/+12 | |
| Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in *that place*, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes #42793. | ||||
| 2017-06-27 | Review comments | Esteban Küber | -4/+0 | |
| - Fix typo - Add docstring - Remove spurious test output file | ||||
| 2017-06-24 | Don't naively point to return type on type error | Esteban Küber | -17/+2 | |
| 2017-06-24 | Do not specify return type in suggestion for some `Ty`s | Esteban Küber | -2/+2 | |
| Don't specify a suggested return type for `TyAnon`, `TyFnDef`, `TyFnPtr`, `TyDynamic`, `TyClosure` and `TyProjection`. | ||||
| 2017-06-24 | Suggest removal of semicolon (instead of being help) | Esteban Küber | -25/+5 | |
| 2017-06-24 | Detect missing `;` on methods with return type `()` | Esteban Küber | -0/+23 | |
| - Point out the origin of a type requirement when it is the return type of a method - Point out possibly missing semicolon when the return type is () and the implicit return makes sense as a statement - Suggest changing the return type of methods with default return type - Don't suggest changing the return type on fn main() - Don't suggest changing the return type on impl fn | ||||
| 2017-06-23 | Move tests to `ui` | Esteban Küber | -0/+499 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |