-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
Specifying an interface in java_send throws a TypeError #2065
Comments
Our interface proxies should be coercible (explicitly or implicitly) to java.lang.Class during dispatch. Might not even need java_send if we did that correctly. |
along the line this has been fixed with some JI ❤️ and the original issue no longer exists :
there's also test-cases for this already ... closing and marking the milestone as 1.7.21 |
is it still ambiguous? ... please check if so open a new issue. thanks |
@kares sure thing |
Calling java_send with an interface as an argument throws a
TypeError
. After a quick discussion with @headius in IRC, it seems like it'd be good if the Ruby representation of an interface could be correctly coerced to a class here.Here's a quick example:
The text was updated successfully, but these errors were encountered: