[CodeComplete] Strip out try and optional eval expo in operator completion #18209
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.
foldSequence()
may hoist these expression up by mutating their sub expression. When completing operators, this behavior ruins reusability of operand. Since these expression doesn't affect completion, we can strip them out.rdar://problem/42452085
Also, this PR contains follow-up fix for f577578. The same treatment for ternary expression (IfExpr). Plus, fix a regression where infix operator were disappeared from results when leading sequence contains
AssignExpr
.