Repository navigation
Fix numeric precision, sequence operations, and rendering safety - #34
Merged
Merged
Conversation
This was referenced Oct 26, 2026
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.
Summary
Fix nine confirmed bugs affecting numeric correctness, sequence operations, and safe template rendering. Each fix includes regression coverage reproducing the original failure, with expected behavior checked against Python Jinja2 where applicable.
Numeric correctness
fromjson; reject unsupported numeric values and trailing JSON content.MinInt64and its filters.sumin integer arithmetic until floating-point promotion is needed.Sequence operations
rangebefore its counter overflows in either direction.select,reject,selectattr, andrejectattrfrom panicking when no explicit test is supplied.Rendering safety
Validation
go vet, Staticcheck, and build pass.Integer arithmetic remains bounded by the engine’s existing
int64support; these changes do not introduce arbitrary-precision arithmetic or general integer-overflow handling.Closes #15, #16, #17, #18, #19, #20, #21, #22, #23.