Fix character literal not storing its contents#106
Merged
alaviss merged 5 commits intoalaviss:mainfrom Jan 11, 2026
Merged
Conversation
alaviss
approved these changes
Jan 11, 2026
Owner
alaviss
left a comment
There was a problem hiding this comment.
LGTM, thanks for contributing!
4088d47 to
e98be1b
Compare
e98be1b to
3c194a8
Compare
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
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 character literal was only storing its contents in a node when it was an escape sequence. Was writing a formatter with topiary but was running into issues with characters since their contents would get lost e.g.