diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-07-20 13:24:54 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-20 13:24:54 +0200 |
| commit | d846e9252c9791f024754811665d66d6c360c818 (patch) | |
| tree | 87481c5b6eaa590e29deb603f5e92125c50dfccb /tests/codegen/src-hash-algorithm/src-hash-algorithm-sha256.rs | |
| parent | 6b9982d4fb05ce20c83540fef1b5048b4f64885e (diff) | |
| parent | 239037ecde3d884ad09bfb95c950021f3bc78da1 (diff) | |
| download | rust-d846e9252c9791f024754811665d66d6c360c818.tar.gz rust-d846e9252c9791f024754811665d66d6c360c818.zip | |
Rollup merge of #127917 - Zalathar:after-or, r=Nadrieril
match lowering: Split `finalize_or_candidate` into more coherent methods I noticed that `finalize_or_candidate` was responsible for several different postprocessing tasks, making it difficult to understand. This PR aims to clean up some of the confusion by: - Extracting `remove_never_subcandidates` from `merge_trivial_subcandidates` - Extracting `test_remaining_match_pairs_after_or` from `finalize_or_candidate` - Taking what remains of `finalize_or_candidate`, and inlining it into its caller --- Reviewing individual commits and ignoring whitespace is recommended. Most of the large-looking changes are just moving existing code around, mostly unaltered. r? ``@Nadrieril``
Diffstat (limited to 'tests/codegen/src-hash-algorithm/src-hash-algorithm-sha256.rs')
0 files changed, 0 insertions, 0 deletions