Fix Refined Method Overloading #62
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
Co-Authored-By: Márcio Caetano <153174341+rodrigomilisse@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Updated
MethodsFunctionsCheckerandOperationsCheckerto include the number of arguments when callingrtc.getContext().getFunction. This change improves function refinement resolution by distinguishing overloaded methods based on their parameter count.Also added a test case, by @rodrigomilisse, which previously threw the exception
"Cannot invoke "liquidjava.processor.context.RefinedFunction.getArguments()" because "f" is null", since it was invoking the wrong method with no parameters.This can be improved in the future by distinguishing methods not only by parameter count but also by parameter types.