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
Switch to Truffle PE mode before calling into Enso #5783
Switch to Truffle PE mode before calling into Enso #5783
Changes from 9 commits
8fcaf60
cddd152
8f0dcb7
9f64dcc
c7d1438
ad9d69c
9910fbc
c3dc114
bc56681
160f324
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.
gotta love Java :)
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.
Why do we need this method instead of putting
throw ex
directly at callsite?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.
Okay, I see that for example
ArityException
orUnsupportedTypeException
extendInteropException
which apparently does not seem to inheritRuntimeException
.So I guess this is the reason for this magic?
But that seems totally unsafe - since we do an unchecked cast to
RuntimeException
of something that we know that it doesn't extendRuntimeException
.If the cast is unchecked, I guess it will go through, but it will violate the typesystem rules. That sounds very worrying at first sight.
Can we get a comment (in the code, as part of this function's doc comment) explaining why we are doing it and why is it safe in this context? (If it is safe...)
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 is a standard way to propagate checked exception thru Java language. Java language has (too) strict rules about checked exceptions, but there is nothing like that in the JVM (as demonstrated by Scala ignoring checked exceptions altogether). Sometimes it is useful to propagate checked exception even the Java method signatures are against it. This is the case. We have to tunnel the exception thru CallTarget interface now. Rather than wrapping the exception into runtime and unpacking it, I am trying to throw it directly. Btw. this is not the first place where this coding technique is used. There are other
raise
methods around the codebase already.