Skip Null Literals in RefinementTypeChecker #63
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>
alcides
requested changes
Oct 21, 2025
Collaborator
alcides
left a comment
alcides
left a comment
There was a problem hiding this comment.
I believe we should use type.equals("..") here.
Kotlin translates == to .equals. But in Java you have to write equals explicitly. == compares object identity while equals compares contents of strings.
Collaborator
Author
|
Absolutely. |
alcides
approved these changes
Oct 21, 2025
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.
Added a condition to skip null literals in the
RefinementTypeChecker, preventing aNotImplementedExceptionwhen encountering null values during refinement checking.