diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-01-19 10:42:12 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-19 10:42:12 +0100 |
| commit | 5d2928f7b9eaea9c00ed7695143c0f71c5f53786 (patch) | |
| tree | f0a6bf47736688b4369e06ae846220a88d43a62a /src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs | |
| parent | 2f004d2d401682e553af3984ebd9a3976885e752 (diff) | |
| parent | 5f74ef4fb1d86d80a3052e772010e613353dbfa7 (diff) | |
| download | rust-5d2928f7b9eaea9c00ed7695143c0f71c5f53786.tar.gz rust-5d2928f7b9eaea9c00ed7695143c0f71c5f53786.zip | |
Rollup merge of #88642 - c410-f3r:let_chains_2, r=matthewjasper
Formally implement let chains ## Let chains My longest and hardest contribution since #64010. Thanks to `@Centril` for creating the RFC and special thanks to `@matthewjasper` for helping me since the beginning of this journey. In fact, `@matthewjasper` did much of the complicated MIR stuff so it's true to say that this feature wouldn't be possible without him. Thanks again `@matthewjasper!` With the changes proposed in this PR, it will be possible to chain let expressions along side local variable declarations or ordinary conditional expressions. In other words, do much of what the `if_chain` crate already does. ## Other considerations * `if let guard` and `let ... else` features need special care and should be handled in a following PR. * Irrefutable patterns are allowed within a let chain context * ~~Three Clippy lints were already converted to start dogfooding and help detect possible corner cases~~ cc #53667
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs')
0 files changed, 0 insertions, 0 deletions