Don't set callInfo when target does not use kwargs#8918
Merged
headius merged 1 commit intojruby:jruby-9.4from Jul 15, 2025
Merged
Don't set callInfo when target does not use kwargs#8918headius merged 1 commit intojruby:jruby-9.4from
headius merged 1 commit intojruby:jruby-9.4from
Conversation
headius
force-pushed
the
no_keywords_no_callinfo
branch
from
676b5e9 to
c360c7c
Compare
Native methods that don't accept formal keyword arguments and Ruby methods that are ruby2_keywords will not use callInfo to handle formal keyword arguments. We clear it here so any incoming kwargs flags do not get stuck and interfere with other calls. Fixes jruby#8782
headius
force-pushed
the
no_keywords_no_callinfo
branch
from
c360c7c to
b983f15
Compare
This was referenced Jul 21, 2025
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
1 participant
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.
Native methods that don't accept formal keyword arguments and Ruby methods that are ruby2_keywords will not use callInfo to handle formal keyword arguments. We clear it here so any incoming kwargs flags do not get stuck and interfere with other calls.
Fixes #8782