-
Notifications
You must be signed in to change notification settings - Fork 334
Fix pattern matching on Java integer field #14458
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
Conversation
hubertp
left a comment
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.
What about Byte, Short, Double?
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 don't think
IsSameObjectNodeis the right place to handle non-longintegers - values allowed to flow in Enso interpreter are
long,double,boolean,TruffleObject
- I am not sure what exactly is
leftorrightin this case - but we certainly don't want any other values than the allowed ones
Yes. The failure was happening when there were two |
| } | ||
|
|
||
| @Specialization | ||
| boolean isSameLong(long left, long right) { |
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.
This looks like the right specialization.
Fixes #14426
Pull Request Description
Fixes pattern matching on Java integer and long fields.
Important Notes
Fallback case branch in
DuckDB_Type_Mapping.ensono longer necessary - removed in 2a84ac4. See #14423 (comment)Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.