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

Age	Commit message (Collapse)	Author	Lines
2023-01-11	Move /src/test to /tests	Albert Larsan	-29/+0

2022-03-08	Change wording of suggestion to add missing `match` arm	Esteban Kuber	-2/+2

2022-03-08	When finding a match expr with a single arm that requires more, suggest it	Esteban Kuber	-2/+10
	Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None \| Some(_) => todo!(), } ```
2022-03-08	When encountering a match expr with no arms, suggest it	Esteban Kuber	-2/+2
	Given ```rust match Some(42) {} ``` suggest ```rust match Some(42) { None \| Some(_) => todo!(), } ```
2020-11-17	Fix exhaustiveness in case a byte string literal is used at slice type	oli	-2/+2

2020-10-18	Destructure byte array constants to array patterns instead of keeping them ↵	Oliver Scherer	-2/+2
	opaque
2020-06-26	Show the values and computation that would overflow a const evaluation or ↵	Oliver Scherer	-2/+2
	propagation
2020-06-13	Prefer the associated consts for pattern matching error	Lzu Tao	-2/+2

2020-03-27	non-exhastive diagnostic: add note re. scrutinee type	Mazdak Farrokhzad	-0/+2

2019-11-21	Use appropriate constructor for const slices	Nadrieril	-4/+4

2019-11-16	Introduce new FixedLenSlice constructor	Nadrieril	-2/+2
	It is used in the case where a variable-length slice pattern is used to match on an array of known size. This allows considering only those entries in the array that are captured by one of the patterns. As a side-effect, diagnostics improve a bit for those cases.
2019-11-05	Make exhaustiveness error message more consistent for slice patterns	Nadrieril	-2/+2
	This improves error messages by indicating when slices above a certain lengths have not been matched. Previously, we would only report examples of such lengths, but of course never all of them.
2019-11-05	Don't use max_slice_length when subtracting from VarLenSlice	Nadrieril	-2/+2
	This alters error messages slightly, but that'll be improved later
2019-10-27	Gather together usefulness tests	Nadrieril	-0/+19
	I took most tests that were testing only for match exhaustiveness, pattern refutability or match arm reachability, and put them in the same test folder.