Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove awkward match in if_let #1725

Merged
merged 3 commits into from
Jun 30, 2024
Merged

Remove awkward match in if_let #1725

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
443fc03
Remove awkward match in if_let
gepbird Jul 5, 2023
5b1e946
Revert "Remove awkward match in if_let"
gepbird Jul 5, 2023
7442728
Remove unnecessary block in awkward match
gepbird Jul 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions src/flow_control/if_let.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,11 +7,7 @@ For some use cases, when matching enums, `match` is awkward. For example:
let optional = Some(7);

match optional {
Some(i) => {
println!("This is a really long string and `{:?}`", i);
// ^ Needed 2 indentations just so we could destructure
// `i` from the option.
},
Some(i) => println!("This is a really long string and `{:?}`", i),
_ => {},
// ^ Required because `match` is exhaustive. Doesn't it seem
// like wasted space?
Expand Down