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

Age	Commit message (Collapse)	Author	Lines
2021-05-12	Show macro name in 'this error originates in macro' message	Aaron Hill	-2/+2
	When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-03-06	Move some tests to more suitable subdirs	Yuki Okushi	-0/+21

2021-02-16	Move some tests to more reasonable directories	Caio	-0/+15

2020-10-11	rustc_parse: More precise spans for `tuple.0.0`	Vadim Petrochenkov	-4/+4

2020-07-02	Add some requested tests	Vadim Petrochenkov	-0/+1

2020-07-02	Update dtolnay's tests that now work	Vadim Petrochenkov	-33/+10

2020-07-02	Add test for errors triggered on parts of decomposed index	David Tolnay	-0/+28

2020-07-02	Add test for tuple indexed with float in macro input	David Tolnay	-0/+20

2020-07-02	Add tests in which the token really is a float	David Tolnay	-0/+21

2020-07-02	Test a range, which is not nested indexing	David Tolnay	-0/+3

2020-07-02	Test even deeper nested indexing	David Tolnay	-0/+3

2020-07-02	Add test of tuple nested indexing	David Tolnay	-0/+6

2020-07-02	parser: Break float tokens into parts in tuple field positions	Vadim Petrochenkov	-21/+0

2020-02-06	rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.	Eduard-Mihai Burtescu	-0/+4

2020-01-09	Update tests	Vadim Petrochenkov	-2/+16

2019-11-26	Refactor 'parse_enum_item' to use 'parse_delim_comma_seq'	Janusz Marcinkiewicz	-3/+9

2019-11-18	Specific labels when referring to "expected" and "found" types	Esteban Küber	-8/+8

2019-11-06	Remove "here" from "expected one of X here"	Esteban Küber	-3/+3

2019-10-27	Gather together usefulness tests	Nadrieril	-23/+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-05-28	Correct pluralisation of tuple/array/associated type binding mismatch errors	varkor	-2/+2

2019-03-11	Update tests	Vadim Petrochenkov	-6/+6

2019-03-02	Point at enum definition when match patterns are not exhaustive	Esteban Küber	-0/+5
	``` 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-01-06	tests: Do not use `-Z parse-only`, continue compilation to test recovery	Vadim Petrochenkov	-3/+1

2018-12-31	Auto merge of #57047 - euclio:field-structured-suggestions, r=estebank	bors	-2/+2
	use structured suggestions for nonexistent fields r? @estebank
2018-12-31	use structured suggestions for nonexistent fields	Andy Russell	-2/+2

2018-12-27	Fix rebase and more CI failures	Vadim Petrochenkov	-2/+2

2018-12-27	Do not abort compilation if expansion produces errors	Vadim Petrochenkov	-6/+24
	Fix a number of uncovered deficiencies in diagnostics
2018-12-25	Remove licenses	Mark Rousskov	-102/+12

2018-08-31	cleanup: Add main functions to some UI tests	Vadim Petrochenkov	-7/+4

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