Use unsafeByteString instead of preEscapedText for ContentRaw#298
Merged
parsonsmatt merged 4 commits intoyesodweb:masterfrom Oct 7, 2025
Merged
Use unsafeByteString instead of preEscapedText for ContentRaw#298parsonsmatt merged 4 commits intoyesodweb:masterfrom
parsonsmatt merged 4 commits intoyesodweb:masterfrom
Conversation
8d7e344 to
692170d
Compare
Contributor
Author
|
Do you feel hesitant to go via some unsafeByteString? I am happy to make it use the lift instance of text values instead. Either way this is a minor but clear win. |
parsonsmatt
approved these changes
Oct 6, 2025
Collaborator
parsonsmatt
left a comment
There was a problem hiding this comment.
This looks good to me - would you mind posting the before generated code too, just so we can see the difference?
Also please make a changelog note
Thanks!
692170d to
ee3bd3d
Compare
Collaborator
|
Awesome, thank you! I think usually |
Collaborator
|
2.1.7 uploaded! |
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.
This PR changes how we generate the code for Hamlet templates.
Currently we generate
Note how we apply Data.Text.pack to the string literal. It works but we can be a little more direct at this point.
With this patch we are now generating leaner code that doesn't have to run pack during runtime and that with inlining can statically allocate the bytestring value (and possibly the Markup value):