-
Notifications
You must be signed in to change notification settings - Fork 439
Fix bugs found by mutating source in SwiftParserTest using alternative token choices #1341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bugs found by mutating source in SwiftParserTest using alternative token choices #1341
Conversation
…have leading trivia
…ate after `resetForSplit`
@swift-ci Please test |
DiagnosticSpec(locationMarker: "1️⃣", message: "expected value and ')' to end tuple"), | ||
DiagnosticSpec(locationMarker: "2️⃣", message: #"unexpected code '"""' in string literal"#), | ||
DiagnosticSpec(locationMarker: "3️⃣", message: #"expected '"""' to end string literal"#), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feels like the """
should be a strong marker that an interpolation is unterminated. But I'm all for this vs an infinite loop 😅.
@@ -1612,11 +1613,12 @@ extension Parser { | |||
modifier = nil | |||
} | |||
|
|||
let introducer = self.eat(handle) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops!
Most of these seem worth cherry-picking to 5.8 (the infinite loop ones at the very least). |
This is a collection of fixes for bugs that I found using the technique in #1340.