diff options
| author | Trevor Gross <t.gross35@gmail.com> | 2025-08-08 14:22:44 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-08 14:22:44 -0500 |
| commit | 18abf3aa44c53652c017752eda43f0405cd22c13 (patch) | |
| tree | 8a515b4f527f6ea90954a14cfeeb1c5bdb9f4532 /compiler/rustc_errors | |
| parent | 6fa6a854cd791e9efa813e9b18cd1a5337ded971 (diff) | |
| parent | 6bf3cbe39e09f4d9187a0b1f6a7bd45101f7aad8 (diff) | |
| download | rust-18abf3aa44c53652c017752eda43f0405cd22c13.tar.gz rust-18abf3aa44c53652c017752eda43f0405cd22c13.zip | |
Rollup merge of #144545 - ChayimFriedman2:bool-witness-order, r=Nadrieril
In rustc_pattern_analysis, put `true` witnesses before `false` witnesses In rustc it doesn't really matter what the order of the witnesses is, but I'm planning to use the witnesses for implementing the "add missing match arms" assist in rust-analyzer, and there `true` before `false` is the natural order (like `Some` before `None`), and also what the current assist does. The current order doesn't seem to be intentional; the code was created when bool ctors became their own thing, not just int ctors, but for integer, 0 before 1 is indeed the natural order. r? `@Nadrieril`
Diffstat (limited to 'compiler/rustc_errors')
0 files changed, 0 insertions, 0 deletions
