Handle basic special characters in write#939
Merged
ashinn merged 2 commits intoashinn:masterfrom Sep 29, 2023
Merged
Conversation
Contributor
Author
|
Ah, it looks like it's not necessary to escape them with their names but we can put any character after |
Owner
|
We should write the descriptive names. We can either use this list or punt to the underlying write like we do for numbers. |
ashinn
approved these changes
Sep 29, 2023
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 fixes the implementation of
writein SRFI 38 with special characters (e.g. newline and tab) as described in the section "6.13.3. Output" in the R7RS.