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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[operators][1/2]feat: Add RelationalOperationExpr to enable equality operators #289
[operators][1/2]feat: Add RelationalOperationExpr to enable equality operators #289
Changes from 10 commits
b9b48ba
02a0aed
dc9ec5c
a9f2589
41af2ae
bd3377a
20688a9
442b463
7aecf47
2e782bc
7d4c396
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Could we please rephrase this so the reader knows what types were expected (similar to the other classes)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am following the Java compiler error message style for operator type-checking. Unlike logical operator, the type-checking is comparatively simple than relational, we could ask for users given boolean type expression. In theory, we could rephrase the error message base on input type condition, like if lhs is numeric type, rhs can only be applied on any numeric type or any numeric boxed type. But it has a lot of condition need to support. Consider of ROI, I wonder if we should follow the Java compiler error message to be consistent with common Java convention.
However, if you prefer to specify the type-checking with detailed error message, we could open a separated ticket and refactor all other type-checking error messages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SG, thanks for the background.