rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2022-03-08	Suggest `if let`/`let_else` for refutable pat in `let`	Esteban Kuber	-1/+5

2022-03-08	Point at uncovered variants in enum definition in `note` instead of a ↵	Esteban Kuber	-10/+9
	`span_label` This makes the order of the output always consistent: 1. Place of the `match` missing arms 2. The `enum` definition span 3. The structured suggestion to add a fallthrough arm
2020-03-27	non-exhastive diagnostic: add note re. scrutinee type	Mazdak Farrokhzad	-0/+1

2020-02-01	Update existing tests for or-patterns	Matthew Jasper	-9/+2

2019-12-14	Revert "Remove `#![feature(never_type)]` from tests."	Niko Matsakis	-2/+2
	This reverts commit 8f6197f39f7d468dfc5b2bd41dae4769992a2f83.
2019-11-21	Remove `#![feature(never_type)]` from tests.	Mazdak Farrokhzad	-2/+2
	Also remove `never_type` the feature-gate test.
2019-10-09	Suggest `if let` on `let` refutable binding	Esteban Küber	-0/+7

2019-09-09	check_match: unify check_irrefutable & check_exhaustive more.	Mazdak Farrokhzad	-0/+1

2019-09-06	Fixed grammar/style in error messages and reblessed tests.	Alexander Regueiro	-2/+2

2019-08-05	Make use of possibly uninitialized data a hard error	Tyler Mandry	-6/+2
	This is one of the behaviors we no longer allow in NLL. Since it can lead to undefined behavior, I think it's definitely worth making it a hard error without waiting to turn off migration mode (#58781). Closes #60450. My ulterior motive here is making it impossible to leave variables partially initialized across a yield (see discussion at #63035), so tests are included for that.
2019-05-21	Add FAQ for NLL migration	Jethro Beekman	-0/+1

2019-04-22	Never stop due to errors before borrow checking	Esteban Küber	-1/+11

2019-03-02	Point at enum definition when match patterns are not exhaustive	Esteban Küber	-2/+9
	``` 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.
2018-12-25	Remove licenses	Mark Rousskov	-1/+1

2018-08-14	Merged migrated compile-fail tests and ui tests. Fixes #46841.	David Wood	-0/+9