Fix missing name for invalid arguments#8375
Merged
Conversation
sovdeeth
approved these changes
Jan 15, 2026
Absolutionism
approved these changes
Feb 1, 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
4 participants
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.
Problem
In some cases, the name of an invalid function argument was not properly carried. For example, given the call
location(1, 1, 1, 100, 100, the error message isCan't understand the argument for world parameter 'null': 100.Solution
When passing arguments through, they are instead recreated with the expected parameter name. I have also tweaked the existing error message.
Testing Completed
I have added an additional test to confirm that the correct parameter name is now printed as expected.
Supporting Information
n/a
Completes: none
Related: none
AI assistance: none