Include an \xHH escape code sequence #709
Closed
Conversation
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
|
Looks good, I'm all for merging! |
* Add TOML 1.0.0-rc.1 * Update README notice, for 1.0.0-rc.1 * Fix link to logo * Update CHANGELOG to reflect release
For starters, to document our release process. Soon, there will be significant restructuring of the contents of this repository, and keeping this documentation updated would help during that migration.
fix some pretty small problem
Clarify that line-ending backslashes are unescaped
* Replace the vague term "expected" with the RFC 2119-compatible terms "should", "must", "required" * Clarify that an error must be thrown if an integer cannot be represented losslessly
Replace "expected" by more precise terms
They're very clearly not adequate, and aren't actually used for anything.
We've not released them in a while, and keeping these around for historical reasons isn't exactly a great idea.
These are now hosted on toml.io, and don't need to be kept in this repository.
Co-authored-by: Christian Siefkes <christian@siefkes.net>
…eparation Add another example of integer grouping
Add changelog entries for recent changes
Per toml-lang#766 this change updates the specification to allow comments with newlines before commas in arrays.
…into i622_backslash_x00
|
Hmm... this seems to have a slightly messed up history here. |
|
I hope I didn't mess anything up. I was trying to bring it up to date. It's still for after v1.0.0, so if a new PR is in order, I can replace this one when the time is right. |
|
Since the history on this PR got messed up, I am replacing it with a new one, #796. The changes to the text (from when it was branched) should be identical to the changes done here. |
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.
Per a conversation in #622, this PR adds a two-character
\xescape code sequence for the first 256 Unicode code points. This provides a short explicit sequence for, among other code points: ASCII characters, certain control characters, and whitespace characters such as tab (\x09) and space (\x20) that need visible representation without resorting to longer\uand\Ucodes. Such sequences are commonly found in languages that also support the\uand\Ucodes for Unicode.