fix: arity checking of call expression arguments - #386
Merged
Conversation
Zipping the arguments with the parameters silently truncated to the shorter of the two. Calling with too few arguments left the unbound parameters resolving to Null, whilst extra arguments were discarded without ever being evaluated, so their side effects never ran. Compare the counts before binding and error with "Wrong number of arguments, want=2, got=1." instead. The check runs before the environment is pushed, so a rejected call leaves no scope behind. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WVqA23HZyr13UowhjHjNEt
DeveloperC286
force-pushed
the
claude/arity-checking-arguments-gu4ewf
branch
from
September 6, 2026 13:22
f6017b4 to
a226869
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.
No description provided.