Merged
Conversation
#933) String interpolation was silently dropping expressions with invalid operators (&, |, ^), returning only the first operand. Now checks for lexer errors and unconsumed tokens after parsing interpolated expressions.
This was
linked to
issues
Jan 7, 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
Collection of bug fixes from January 7, 2026.
Included Fixes
fix(interpreter): allow arbitrary precision arithmetic for int/uint types (#917)
intanduinttypes are backed bybig.Intbut arithmetic operations were incorrectly capping at i64/u64 boundsfix(typechecker): show correct error for invalid sized types with using directive (#914)
usingdirective was present, undefined types likei512showed "type mismatch" instead of "undefined type"fix(parser): error on invalid operators in string interpolation (#916)
&,|,^)Test plan