-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Reject bad string interpolations #17074
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
640e2bb
Reject bad string interpolations
beccadax fac5d72
Tweak error name to match message
beccadax 42d2f67
Diagnose empty interpolations more clearly
beccadax f278100
Don’t double-diagnose parse errors
beccadax 4a42938
Fix incorrect test RUN: line
beccadax 0674be6
Update comment
beccadax 5297c91
Add more argument label tests
beccadax a071c65
Resolve the SR-7958 crasher test
beccadax File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
// RUN: %target-typecheck-verify-swift | ||
|
||
let str = "a" | ||
|
||
// Test with too many interpolated values. | ||
func papaBear() { | ||
_ = "\(str, str)" // expected-error{{interpolations should be a single expression}} expected-note {{insert parentheses to form a tuple}} {{9-9=(}} {{19-19=)}} | ||
} | ||
|
||
// Test with too few interpolated values. | ||
func mamaBear() { | ||
_ = "\()" // expected-error{{interpolations should be a single expression}} expected-note {{delete empty interpolation}} {{8-11=}} | ||
} | ||
|
||
// Test with the correct number of interpolated values. | ||
func babyBear() { | ||
_ = "\(str)" | ||
} | ||
|
||
// Test with an argument label | ||
func funkyBear() { | ||
_ = "\(describing: str)" // expected-error{{interpolations cannot start with a keyword argument}} {{10-22=}} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A suggestion: Try another There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done. |
||
_ = "\(format: str)" // expected-error{{interpolations cannot start with a keyword argument}} {{10-18=}} | ||
_ = "\(validatingUTF8: str)" // expected-error{{interpolations cannot start with a keyword argument}} {{10-26=}} | ||
_ = "\(fnord: str)" // expected-error{{interpolations cannot start with a keyword argument}} {{10-17=}} | ||
} |
2 changes: 1 addition & 1 deletion
2
...est/compiler_crashers_2/0160-sr7958.swift → ...mpiler_crashers_2_fixed/0160-sr7958.swift
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
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.
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.
Is the expression ever not a TupleExpr? Maybe use cast<> here instead?
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.
The expression actually should be a ParenExpr. I don’t know of a reason it should be a TupleExpr without one of the nested conditions being true, but if it ever was, as far as I know it would be valid.