This repository has been archived by the owner on Jan 27, 2025. It is now read-only.
Refactor unwrap() with Match #1164
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replaced Match with expect
|
Thx a lot for the effort, looks good to me. And if the main purpose of this task was not to exit or panic, then we would use match (or ? operator) to return the error to caller (or handle the error) instead of expect/unwrap which stops the program in case of error. FYI. |
In line with the Tool Scrubber Guild lessons, went for match / ? rather than expect
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First attempt to refactor unwrap() with Match
Related PRs
#1144