ascii=true and fullhex=true flags for escape_string #55099
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.
This PR adds two new optional keyword flags
ascii=true
andfullhex=true
to theescape_string
function, both of which default tofalse
(= current behavior).If
ascii=true
is passed, then all non-ASCII characters are escaped. Iffullhex=true
is passed, then\u
and\U
escapes are printed with 4- and 8-digit hex values, respectively (instead of omitting leading zeros).Motivation:
"äöü"
is written in NFC normalization"\u00e4\u00f6\u00fc"
or NFD normalization"a\u0308o\u0308u\u0308"
, and don't want to run the risk of an editor accidentally re-normalizing the string for you (as happens in some browsers), you have to write it escaped.