about summary refs log tree commit diff
path: root/src/test/ui/pattern/usefulness
AgeCommit message (Collapse)AuthorLines
2020-04-11rustc: Add a warning count upon completionRoccoDev-1/+3
2020-04-02tests: remove ignore directives from tests that mention core/alloc/std spans.Eduard-Mihai Burtescu-27/+12
2020-03-27non-exhastive diagnostic: add note re. scrutinee typeMazdak Farrokhzad-0/+108
2020-03-23Ignore tests on some platforms due to #53081Aaron Hill-12/+27
2020-03-22Store idents for `DefPathData` into crate metadataAaron Hill-0/+18
Previously, we threw away the `Span` associated with a definition's identifier when we encoded crate metadata, causing us to lose location and hygiene information. We now store the identifier's `Span` in the crate metadata. When we decode items from the metadata, we combine the name and span back into an `Ident`. This improves the output of several tests, which previously had messages suppressed due to dummy spans. This is a prerequisite for #68686, since throwing away a `Span` means that we lose hygiene information.
2020-03-17Update tests for erasing regions in typeckMatthew Jasper-2/+2
2020-01-24Normalise notes with the/isvarkor-17/+17
2020-01-20check_match: simplify check_armMazdak Farrokhzad-1/+3
2020-01-18slice_patterns: organize some testsMazdak Farrokhzad-0/+11
2020-01-18slice_patterns: remove gates in testsMazdak Farrokhzad-68/+55
2020-01-09Update testsVadim Petrochenkov-2/+24
2019-12-14Revert "Remove `#![feature(never_type)]` from tests."Niko Matsakis-1/+2
This reverts commit 8f6197f39f7d468dfc5b2bd41dae4769992a2f83.
2019-12-11Revert a diagnostic change in the case of integer rangesNadrieril-8/+8
2019-12-04Reuse `adt_defined_here`Nadrieril-10/+43
2019-12-04Use the default code path to list missing patternsNadrieril-48/+60
This uses the exact same code path that would be used for `match x { _ if false => {} }`, since in both cases the resulting matrix is empty. Since we think the behaviour in that case is ok, then we can remove the special case and use the default code path.
2019-12-04List missing constructors in an almost empty matchNadrieril-71/+101
Actually empty matches are still handled by a different code path
2019-12-04Add testsNadrieril-65/+312
2019-12-04Only warn about missing patterns in the case of an enumNadrieril-80/+26
2019-12-04Add testsNadrieril-16/+104
2019-12-04Make empty match lint more consistent under exhaustive_patternsNadrieril-25/+58
2019-12-04Fix erroneous commentNadrieril-8/+7
2019-12-04Tweak error on empty matchNadrieril-2/+2
2019-12-04Add testsNadrieril-0/+229
2019-12-02Remove top-level or-pattern hackNadrieril-12/+5
2019-12-02Correct error on partially unreachable or-pat in `if let`Nadrieril-15/+12
2019-12-02Add some testsNadrieril-0/+134
2019-11-28Auto merge of #66603 - Nadrieril:fix-65413, r=varkorbors-7/+81
Fix #65413 #65413 was due to an oversight in `pat_constructor` that didn't check if a particular const value was maybe a slice/array const.
2019-11-21Remove `#![feature(never_type)]` from tests.Mazdak Farrokhzad-2/+1
Also remove `never_type` the feature-gate test.
2019-11-21Use appropriate constructor for const slicesNadrieril-23/+9
2019-11-21Add some testsNadrieril-3/+91
2019-11-17Small improvement to exhaustiveness diagnosticsNadrieril-6/+6
2019-11-16Introduce new FixedLenSlice constructorNadrieril-11/+11
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-16Add some testsNadrieril-23/+49
2019-11-15Add regression testNadrieril-0/+6
2019-11-15Apply suggestions from code reviewNadrieril Feneanar-1/+1
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
2019-11-15Add test for failing `try_eval_bits`Nadrieril-1/+16
2019-11-06Split slice-patterns test as suggested by CentrilNadrieril-89/+109
2019-11-05Move a few more tests to the usefulness/ folderNadrieril-0/+193
2019-11-05Use VarLenSlice consistently when splitting constructorsNadrieril-21/+21
The previous behaviour ignored slice lengths above a certain length because it could not do otherwise. We now have VarLenSlice however, that can represent the ignored lengths to make the algorithm more consistent. This does not change the correctness of the algorithm, but makes it easier to reason about. As a nice side-effect, exhaustiveness errors have improved: they now capture all missing lengths instead of only the shortest.
2019-11-05Add some test casesNadrieril-1/+31
2019-11-05Make exhaustiveness error message more consistent for slice patternsNadrieril-11/+11
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-05Don't use max_slice_length when subtracting from VarLenSliceNadrieril-2/+2
This alters error messages slightly, but that'll be improved later
2019-11-05Add some slice-pattern exhaustiveness testsNadrieril-0/+213
2019-11-02Update error annotations in tests that successfully compileTomasz Miąsko-2/+2
Those annotation are silently ignored rather than begin validated against compiler output. Update them before validation is enabled, to avoid test failures.
2019-10-27Gather together usefulness testsNadrieril-0/+2044
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.