about summary refs log tree commit diff
path: root/src/test/ui/pattern/usefulness/match-byte-array-patterns-2.stderr
AgeCommit message (Collapse)AuthorLines
2020-11-17Fix exhaustiveness in case a byte string literal is used at slice typeoli-2/+2
2020-10-18Destructure byte array constants to array patterns instead of keeping them ↵Oliver Scherer-2/+2
opaque
2020-06-26Show the values and computation that would overflow a const evaluation or ↵Oliver Scherer-2/+2
propagation
2020-06-13Prefer the associated consts for pattern matching errorLzu Tao-2/+2
2020-03-27non-exhastive diagnostic: add note re. scrutinee typeMazdak Farrokhzad-0/+2
2019-11-21Use appropriate constructor for const slicesNadrieril-4/+4
2019-11-16Introduce new FixedLenSlice constructorNadrieril-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-05Make exhaustiveness error message more consistent for slice patternsNadrieril-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-05Don't use max_slice_length when subtracting from VarLenSliceNadrieril-2/+2
This alters error messages slightly, but that'll be improved later
2019-10-27Gather together usefulness testsNadrieril-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.