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
extend FFI::Library doesn't extend some methods into module #1529
Comments
It seems to be similar to #1524 |
Our current implementation of FFI (using Truffle NFI) is not complete, so this means we did not implement that method yet. |
@eregon Are you sure? Because in case of |
In fact I've seen more issues like |
@deepj The |
@eregon I see, got it. |
This is also an issue for |
@eregon @chrisseaton if there would be a chance to move FFI compability forward it could help to run more native gems on TruffleRuby. RC13/14? |
I think we're unlikely to fix this one as fast as the other priority issues, I'm afraid. It's going to be a bit more work. |
I'm going to remove the priority tag on this, as we aren't going to be able to solve it in the next month or so, which is what we're aiming at with priority issues now. |
I fixed this in 59fb511 and added complete support for the FFI, with a pure-Ruby implementation using Truffle NFI. |
There is no issue under MRI. After initializing the module,
TestModule': undefined method 'callback' for TestModule:Module (NoMethodError)
exception is occurred. The code below tries to call this method https://www.rubydoc.info/github/ffi/ffi/FFI/Library#callback-instance_methodThis is a small reproducible example of issue comes from https://github.com/libvips/ruby-vips/blob/428d5c106fb4a64521159c6b0c4f9391eea2eba6/lib/vips.rb#L36
Error:
The text was updated successfully, but these errors were encountered: