rust/src/test/ui/tuple, branch 1.40.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.40.02019-10-27T21:20:26+00:00Gather together usefulness tests2019-10-27T21:20:26+00:00Nadrierilnadrieril@gmail.com2019-09-28T14:05:38+00:00urn:sha1:09f9947ebc68a8199c3dff8607a41571c48cc377
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.
Correct pluralisation of tuple/array/associated type binding mismatch errors2019-05-28T20:35:20+00:00varkorgithub@varkor.com2019-05-27T13:28:20+00:00urn:sha1:56181cf8abf8ad7f7d36e92ef4d7bf294df23c4cUpdate tests2019-03-11T20:10:26+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2019-03-09T12:03:44+00:00urn:sha1:fa72a81bea27f1fda4287475e4cc2f684c971e7fPoint at enum definition when match patterns are not exhaustive2019-03-03T00:45:23+00:00Esteban Küberesteban@kuber.com.ar2019-02-10T13:12:00+00:00urn:sha1:0081ef2548f95171b33bbaedcd90253cf41916b2
```
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.
tests: Do not use `-Z parse-only`, continue compilation to test recovery2019-01-06T19:20:46+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2019-01-06T15:33:05+00:00urn:sha1:1f64f60d5cba64beca6e812e16d6d99519d3551bAuto merge of #57047 - euclio:field-structured-suggestions, r=estebank2018-12-31T20:56:19+00:00borsbors@rust-lang.org2018-12-31T20:56:19+00:00urn:sha1:9eac386342c601b14311b435f2b6d314fc817bb5
use structured suggestions for nonexistent fields
r? @estebank
use structured suggestions for nonexistent fields2018-12-31T17:52:30+00:00Andy Russellarussell123@gmail.com2018-12-20T23:10:46+00:00urn:sha1:dfc326d0e212bd644d04906ca21bb012cf970cb4Fix rebase and more CI failures2018-12-27T12:51:37+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2018-12-27T00:07:00+00:00urn:sha1:bc16edeb28e38e5bbed8828fb6314b1cc5151235Do not abort compilation if expansion produces errors2018-12-27T12:51:36+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2018-12-16T17:23:27+00:00urn:sha1:fff01ccfa805ccef67827bf1ea84e21d61d13e6f
Fix a number of uncovered deficiencies in diagnostics
Remove licenses2018-12-26T04:08:33+00:00Mark Rousskovmark.simulacrum@gmail.com2018-12-25T15:56:47+00:00urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718c