Small refactoring improvements around ExprFlavor
#2103
Merged
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.
forDirective
withExprFlavor
, getting rid of one boolean parameter in expression parsingExprFlavor.basic
->stmtCondition
because this case is used primarily in statement conditions that need to disambiguate trailing closures from the statement’s bodyExprFlavor.trailingClosure
->basic
because this is the base case that we use inside normal expression parsingflavor
to match thepattern
parameter that also has a label and makeparseExpression
parameters required so that each caller needs to make a conscious choice about the values and so it’s easier to search for where each of the flavors is being used.