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

Age	Commit message (Collapse)	Author	Lines
2019-10-27	Gather together usefulness tests	Nadrieril	-123/+0
	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.
2019-10-16	Lint only on single element overlap	Esteban Küber	-15/+7

2019-10-16	Only emit overlapping patterns lint if the overlap is partial	Esteban Küber	-18/+10

2019-10-16	Continue to emit unreachable pattern on cases caught by overlapping patterns	Esteban Küber	-10/+16

2019-10-16	Move overlapping patterns to its own lint	Esteban Küber	-1/+7

2019-10-16	Add check for overlapping ranges to unreachable patterns lint	Esteban Küber	-7/+25

2019-08-06	pretty-pretty extremal constants!	Zack M. Davis	-14/+14
	While many programmers may intuitively appreciate the significance of "magic numbers" like −2147483648, Rust is about empowering everyone to build reliable and efficient software! It's a bit more legible to print the constant names (even noisy fully-qualified-paths thereof). The bit-manipulation methods mirror those in `librustc_mir::hair::pattern::_match::all_constructors`; thanks to the immortal Varkor for guidance. Resolves #56393.
2019-03-11	Update tests	Vadim Petrochenkov	-13/+13

2019-03-02	Point at enum definition when match patterns are not exhaustive	Esteban Küber	-0/+22
	``` 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	-14/+14

2018-11-30	Separate out precise_pointer_size_matching tests from ↵	varkor	-8/+8
	exhaustive_integer_patterns tests
2018-11-30	Update existing tests with more precise error messages	varkor	-14/+14

2018-08-21	Add some extra edge case tests	varkor	-1/+13

2018-08-21	Add a test case for u128::MAX - 1	varkor	-1/+7

2018-08-16	Add some more compound exhaustiveness tests	varkor	-1/+7

2018-08-16	Add a test for integer products	varkor	-1/+7

2018-08-16	Add guarded arms to tests	varkor	-1/+7

2018-08-16	Replace ... with ..= in suggestions	varkor	-6/+6
	As ... is "(silently) deprecated". Presumably this means we should be giving correct, up-to-date suggestions, though.
2018-08-16	Fix sign conversion arithmetic errors	varkor	-2/+2

2018-08-16	Add singleton patterns to test	varkor	-2/+14

2018-08-16	Fix range splitting	varkor	-4/+4

2018-08-16	Add semi-exhaustive tests for exhaustiveness	varkor	-0/+39