| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-04-18 | hide `--explain` hint if error has no extended info | Andy Russell | -1/+1 | |
| 2019-04-12 | Stabilize the `alloc` crate. | Simon Sapin | -2/+2 | |
| This implements RFC 2480: * https://github.com/rust-lang/rfcs/pull/2480 * https://github.com/rust-lang/rfcs/blob/master/text/2480-liballoc.md Closes https://github.com/rust-lang/rust/issues/27783 | ||||
| 2019-03-11 | Update tests | Vadim Petrochenkov | -9/+9 | |
| 2019-03-02 | Point at enum definition when match patterns are not exhaustive | Esteban Küber | -2/+10 | |
| ``` error[E0004]: non-exhaustive patterns: type `X` is non-empty --> file.rs:9:11 | 1 | / enum X { 2 | | A, | | - variant not covered 3 | | B, | | - variant not covered 4 | | C, | | - variant not covered 5 | | } | |_- `X` defined here ... 9 | match x { | ^ | = help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms error[E0004]: non-exhaustive patterns: `B` and `C` not covered --> file.rs:11:11 | 1 | / enum X { 2 | | A, 3 | | B, 4 | | C, | | - not covered 5 | | } | |_- `X` defined here ... 11 | match x { | ^ patterns `C` not covered ``` When a match expression doesn't have patterns covering every variant, point at the enum's definition span. On a best effort basis, point at the variant(s) that are missing. This does not handle the case when the missing pattern is due to a field's enum variants: ``` enum E1 { A, B, C, } enum E2 { A(E1), B, } fn foo() { match E2::A(E1::A) { E2::A(E1::B) => {} E2::B => {} } //~^ ERROR `E2::A(E1::A)` and `E2::A(E1::C)` not handled } ``` Unify look between match with no arms and match with some missing patterns. Fix #37518. | ||||
| 2019-02-08 | Use descriptive variant name | varkor | -5/+5 | |
| 2019-02-07 | Improve the error messages for missing stability attributes | varkor | -5/+5 | |
| This makes the capitalisation consistent and provides more context (especially for missing top-level attributes). | ||||
| 2018-12-30 | Tweak E0308 error for clarity | Esteban Küber | -1/+1 | |
| 2018-12-30 | Point at function name span | Esteban Küber | -1/+3 | |
| 2018-12-30 | Point at the return type span on type mismatch due to missing return | Esteban Küber | -2/+2 | |
| Do not point at the entire block span on fn return type mismatches caused by missing return. | ||||
| 2018-12-25 | Remove licenses | Mark Rousskov | -186/+15 | |
| 2018-11-07 | Removed `#[rustc_error]` from tests that are all `// compile-pass`. | Felix S. Klock II | -13/+5 | |
| I also added `// skip-codegen` to each one, to address potential concerns that this change would otherwise slow down our test suite spending time generating code for files that are really just meant to be checks of compiler diagnostics. (However, I will say: My preference is to not use `// skip-codegen` if one can avoid it. We can use all the testing of how we drive LLVM that we can get...) (Updated post rebase.) | ||||
| 2018-10-28 | Use token description in "expected/found" parse messages | Esteban Küber | -2/+3 | |
| 2018-08-23 | add #[panic_handler]; deprecate #[panic_implementation] | Jorge Aparicio | -4/+4 | |
| 2018-08-14 | Merged migrated compile-fail tests and ui tests. Fixes #46841. | David Wood | -0/+535 | |
