[5.5][Parse] Don't skip '}' when recovering from 'default' outside 'switch' #38115
Conversation
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
That caused assertion failures in code completion. rdar://78781163 (cherry picked from commit aa182ac)
|
@swift-ci Please test |
|
@swift-ci Please nominate |
DougGregor
approved these changes
Jun 29, 2021
|
Windows failure was unrelated. Merging. |
AnthonyLatsis
added
🍒 release cherry pick
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.
Cherry-pick #38036 into
release/5.5caseordefaultoutsideswitchstatement, it skips to the next:or EOF ignoring the end of the function body (i.e.}). This behavior is not only undesirable for the error recovery, but causes an assertion failure in code completion.case/defaultoutsideswitch