simplify a switch statement#70
Closed
glessard wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Superseded by #71 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change has no effect on functionality, documentation or testing.
The switch in
ArgumentSet.flagUpdate(originally in one of the Flag constructors) switches on 3 items, one of which (the return value ofvalues.element(forKey:)) is needed in only one of the 12 possibilities. This moves the call tovalues.element(forKey:)into the onecasewhere it is needed. The function becomes slightly more efficient, and theswitchis more readable (down to 6 possibilities), and no longer needs adefaultcase. Note that the probably-impossible failure mode wherevalues.element(forKey: keyreturnsnilandhasUpdatedistruestill results in the same behaviour, namely the argument is unused and the function returnstrue; this eventually leads to a call toErrorMessageGenerator.unknownOptionMessage.Checklist