From 1c36b5d7718b19d094fc0c26e3a450838b6a7615 Mon Sep 17 00:00:00 2001 From: Igor Petruk Date: Mon, 23 Jan 2023 18:05:06 +0000 Subject: [PATCH] Update if-let-expressions.md (#237) Mention `let else` in the speaker notes. --- src/control-flow/if-let-expressions.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/control-flow/if-let-expressions.md b/src/control-flow/if-let-expressions.md index 813a49a4..9c9a9c6d 100644 --- a/src/control-flow/if-let-expressions.md +++ b/src/control-flow/if-let-expressions.md @@ -19,6 +19,7 @@ Rust.
* `if let` can be more concise than `match`, e.g., when only one case is interesting. In contrast, `match` requires all branches to be covered. + * For the similar use case consider demonstrating a newly stabilized [`let else`](https://github.com/rust-lang/rust/pull/93628) feature. * A common usage is handling `Some` values when working with `Option`. * Unlike `match`, `if let` does not support guard clauses for pattern matching.