Improve error messages when using SyntaxStringInterpolation with invalid syntax code #855
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.
If parsing source text of a
SyntaxStringInterpolation
produced a tree with errors or did not consume all characters in the string literal (and would thus drop text), raise a fatal error.To make sure parsing errors are displayed at the string literal itself and don’t navigate Xcode to the
SyntaxExpressibleByStringInterpolation
initializer thatfatalError
ed, split the initializer into a throwing variant and a@_transparent
one thatfatalError
s when the throwing initializer encounters an error. Because@_transparent
is also transparent in terms of source locations, this will make the crash appear at the start of the string literal.Example error messages