diff options
| author | Samuel Tardieu <sam@rfc1149.net> | 2025-08-23 22:22:15 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-23 22:22:15 +0200 |
| commit | 5a14685a63b8306367c3fdd49717113e9ba0ba59 (patch) | |
| tree | 4d4917ba42f5f53339d21e5de9d15e598b6ed533 /tests/codegen-llvm/src-hash-algorithm/src-hash-algorithm-sha256.rs | |
| parent | 982b022b1e713ddff01071bd0538329b279c788b (diff) | |
| parent | 8f649a7e585f03e69c61a5b8286a61b38307afe8 (diff) | |
| download | rust-5a14685a63b8306367c3fdd49717113e9ba0ba59.tar.gz rust-5a14685a63b8306367c3fdd49717113e9ba0ba59.zip | |
Rollup merge of #145234 - dianne:1-tuple-witnesses, r=jackh726
match exhaustiveness diagnostics: show a trailing comma on singleton tuple consructors in witness patterns (and clean up a little) Constructor patterns of type `(T,)` are written `(pat,)`, not `(pat)`. However, exhaustiveness/usefulness diagnostics would print them as `(pat)` when e.g. providing a witness of non-exhaustiveness and suggesting adding arms to make matches exhaustive; this would result in an error when applied. rust-analyzer already prints the trailing comma, so it doesn't need changing. This also includes some cleanup in the second commit, with justification in the commit message.
Diffstat (limited to 'tests/codegen-llvm/src-hash-algorithm/src-hash-algorithm-sha256.rs')
0 files changed, 0 insertions, 0 deletions