Improve char escaping in lexer messages #47914
Merged
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.
Currently
'
,"
and\
are escaped as\'
,\"
and\\
respectively. This leads to confusing messages such aserror: unknown start of token: \\
when encountering a single backslash.Fix by emitting printable ASCII characters directly. This will still escape
\r
,\n
,\t
and Unicode characters.Fixes #47902