-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Create and export rust C API from the runtime #1682
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Will also need to start installing a header file |
This may not be needed (at least yet) with #1732 |
Punting for now since we have callbacks from C. |
I'm interested in integrating event loops and I/O channels with foreign code (GLib/Gio). #4419 would hopefully provide a solution to "get the global/thread-local event loop that the other libraries are using and hook into it". Conversely, there could be an official way to get message channels from the Rust C API, and extract file descriptors/handles to add to an event loop in the foreign code. |
I don't believe this is backwards incompatible, renominating. |
this seems more like a relic from days of stronger dependency on a specific runtime, closing |
More and more people are wanting to interop with the Rust runtime from C code. We need to create a suitable interface for doing such, and not encourage using the builtins or upcalls. I propose using the
rust_client_
namespace orrust_api_
.Current functions being abused:
The text was updated successfully, but these errors were encountered: