-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Support finding a compiled api with API::UNSPECIFIED #116
Comments
nevermind, I didn't push the change for observers |
Patch looks sound nevertheless, will apply |
btw, are you ok with me linking the bindings in the README ? :) |
Thanks for addressing this! Linking is fine with me. Would you be open to exposing more methods in the C API? For example, finding which APIs are available, and what their names are. At the moment I’m trying to but the new bindings to use, but I might have time later to send a patch for those new methods. |
yes definitely, the C api is very provisional right now and not stable yet. For instance all the names aren't homogenous. Stable version will be part of the 5.0 release. |
heya! I just added some of the requested methods. there will still be a bit of breakage before stable release.. |
Thank you. I am still wrangling foreign pointers and the Haskell side! Will pull and try the new methods soon. |
Hello, I'm working on Haskell FFI bindings for this library and found that using
API::UNSPECIFIED
doesn't quite behave as I expect. Creating an observer simply fails, rather than picking a valid API. Here's a diff that works for me:Is this the solution?
Thanks!
The text was updated successfully, but these errors were encountered: