Add option to create an OpalVal in Java#172
Merged
schlichtig merged 2 commits intodevelopfrom Jun 20, 2025
Merged
Conversation
schlichtig
approved these changes
Jun 20, 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
2 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.
Currently, it is not possible to create an
OpalValin a Java program because we enforce a generic type on the underlying expression. Since Java does not understand Scala's generic type system, one must use explicit typesExpr[TacLocal]and cannot use something likeExpr[Nothing]. To deal with this problem, this PR adds an "unsafe" way that allows to ignore the generic type in Java programs by doing the cast in the Scala program