diff options
author | bors <bors@rust-lang.org> | 2021-10-19 14:41:39 +0000 |
---|---|---|
committer | bors <bors@rust-lang.org> | 2021-10-19 14:41:39 +0000 |
commit | 1af55d19c7a9189374d89472f97dc119659bb67e (patch) | |
tree | 0b57780548a1db2ad0f8c171bd68fea92873aa2d /tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs | |
parent | c2452de12046850b8d4c00ce361569b24ad3ad8d (diff) | |
parent | ef018be5c49d7a0bb8ad8e3485111e8b2ab9c5ac (diff) | |
download | rust-1af55d19c7a9189374d89472f97dc119659bb67e.tar.gz |
Auto merge of #89933 - est31:let_else, r=michaelwoerister
Adopt let_else across the compiler
This performs a substitution of code following the pattern:
```
let <id> = if let <pat> = ... { identity } else { ... : ! };
```
To simplify it to:
```
let <pat> = ... { identity } else { ... : ! };
```
By adopting the `let_else` feature (cc #87335).
The PR also updates the syn crate because the currently used version of the crate doesn't support `let_else` syntax yet.
Note: Generally I'm the person who *removes* usages of unstable features from the compiler, not adds more usages of them, but in this instance I think it hopefully helps the feature get stabilized sooner and in a better state. I have written a [comment](https://github.com/rust-lang/rust/issues/87335#issuecomment-944846205) on the tracking issue about my experience and what I feel could be improved before stabilization of `let_else`.
Diffstat (limited to 'tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs')
0 files changed, 0 insertions, 0 deletions