Address part of #11: Fully embrace RFC 8949 encoding indicator syntax #15
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
* Remove spurious spaces in front of them * Allow them behind all strings and numbers * Allow then right after the tag number * Add embedded to the bstr choice (So now also allow them in streamstring) Still need to address ei within streamstring
Closed
With app-string in the picture, there no longer is a syntactic way to check that the chunks of streamstrings are all text or all bytes.
cabo
changed the title
This was referenced Oct 8, 2023
chrysn
approved these changes
Oct 9, 2023
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.
Encoding Indicator within streamstring addressed in commit below.
With app-string in the picture, there no longer is a syntactic way to
check that the chunks of streamstrings are all text or all bytes.