Fix unlabeled arg execution order #8184
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
CodSpeed Instrumentation Performance ReportMerging #8184 will not alter performanceComparing Summary
|
nrc
approved these changes
Aug 29, 2025
jtran
force-pushed
the
jtran/fix-unlabeled-order
branch
from
ea06f65 to
3dad2f9
Compare
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.
Before, unlabeled args like
one()would get executed after labeled argumentstwo()andthree(). Execution order was:two()three()one()fooThis PR makes it in left-to-right order.
fooone()two()three()This is a breaking change due to things like #2728, but I don't think many KCL programs rely on the current behavior. I think it's worth it to change.