about summary refs log tree commit diff
path: root/tests/ui/or-patterns
AgeCommit message (Collapse)AuthorLines
2024-12-12Filter empty lines, comments and delimiters from previous to last multiline ↵Esteban Küber-1/+0
span rendering
2024-11-23Update tests for new TRPL chapter orderChris Krycho-1/+1
2024-10-28Tweak more warnings.Nicholas Nethercote-4/+4
Much like the previous commit. I think the removal of "the token" in each message is fine here. There are many more error messages that mention tokens without saying "the token" than those that do say it.
2024-08-19Reword the "unreachable pattern" explanationsNadrieril-68/+68
2024-07-24Improve "covered_by_many" errorNadrieril-7/+51
2024-07-24Explain why a given pattern is considered unreachableNadrieril-63/+168
2024-07-12Make parse error suggestions verbose and fix spansEsteban Küber-40/+249
Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts.
2024-06-16Add testsNadrieril-16/+47
2024-02-16[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives许杰友 Jieyou Xu (Joe)-37/+37
2024-02-08Continue to borrowck even if there were previous errorsOli Scherer-28/+62
2024-01-18Consistently warn unreachable subpatternsNadrieril-4/+18
2024-01-18Add testsNadrieril-1/+43
2024-01-13Bless testsGeorge-lewis-0/+1
Update tests
2023-12-07recurse into refs when comparing tys for diagnosticsjyn-2/+2
2023-11-26Auto merge of #117611 - Nadrieril:linear-pass-take-4, r=cjgillotbors-27/+66
Rewrite exhaustiveness in one pass This is at least my 4th attempt at this in as many years x) Previous attempts were all too complicated or too slow. But we're finally here! The previous version of the exhaustiveness algorithm computed reachability for each arm then exhaustiveness of the whole match. Since each of these steps does roughly the same things, this rewrites the algorithm to do them all in one go. I also think this makes things much simpler. I also rewrote the documentation of the algorithm in depth. Hopefully it's up-to-date and easier to follow now. Plz comment if anything's unclear. r? `@oli-obk` I think you're one of the rare other people to understand the exhaustiveness algorithm? cc `@varkor` I know you're not active anymore, but if you feel like having a look you might enjoy this :D Fixes https://github.com/rust-lang/rust/issues/79307
2023-11-24Show number in error message even for one errorNilstrieb-4/+4
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-11-22Add some testsNadrieril-27/+66
2023-10-30Correctly handle nested or-patterns in column-wise analysesNadrieril-0/+6
2023-10-12Detect ruby-style closure in parserEsteban Küber-1/+7
When parsing a closure without a body that is surrounded by a block, suggest moving the opening brace after the closure head. Fix #116608.
2023-10-02Replace `HashMap` with `IndexMap` in pattern binding resolveNilstrieb-42/+42
It will be iterated over, so we should avoid using `HashMap`.
2023-08-18Bless test changesGary Guo-34/+34
2023-05-21Rename `drop_ref` lint to `dropping_references`Urgau-1/+1
2023-05-21Rename `drop_copy` lint to `dropping_copy_types`Urgau-1/+1
2023-05-10Adjust tests for new drop and forget lintsUrgau-0/+2
2023-05-01Rip it outNilstrieb-22/+16
My type ascription Oh rip it out Ah If you think we live too much then You can sacrifice diagnostics Don't mix your garbage Into my syntax So many weird hacks keep diagnostics alive Yet I don't even step outside So many bad diagnostics keep tyasc alive Yet tyasc doesn't even bother to survive!
2023-04-27Provide RHS type hint when reporting operator errorMichael Goulet-2/+2
2023-04-03Perform match checking on THIR.Camille GILLOT-6/+6
2023-01-30Modify primary span label for E0308Esteban Küber-5/+5
The previous output was unintuitive to users.
2023-01-11Migrate pattern matchingmejrs-1/+1
2023-01-11Move /src/test to /testsAlbert Larsan-0/+2978