Parse escape sequeces in macros #47
Open
Conversation
This file contains 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
If a string with escape sequences is passed any macro this will
parse the escapes. This will parse all escapes listed in the rust
reference except for \u{XXXX} Unicode escapes because non ascii is not
supported
All in the name of not adding syn to Cargo.toml
|
Would it be possible to rely on the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The sketchy string literal parser is now less sketchy!
If a string with escape sequences is passed to any macro this patch will
parse the escapes. It will parse all escapes listed in the rust
reference except for
\u{XXXX}Unicode escapes because they are complicated and non-ASCII isexplicitly unsupported.
All in the name of not adding syn to Cargo.toml.