The polyglot bindings generator for your library.
Write a robust library in Rust, easily access it from your second-favorite language:
- Design a single
.dll/.soin Rust, consume it from anywhere. - Get QoL features (e.g., classes, strings) in languages that have them.
- Always have a sane, C-compatible API.
- Painless workflow, no external tooling required.
- Easy to support more languages, backends fully decoupled from main project.
We strive to make our generated bindings zero cost. They should be as idiomatic as you could have reasonably written them yourself, but never magic or hiding the interface you actually wanted to expose.
use interoptopus::{ffi_function, ffi_type, Inventory, InventoryBuilder, function};
#[ffi_type]
#[repr(C)]
pub struct Vec2 {
pub x: f32,
pub y: f32,
}
#[ffi_function]
#[no_mangle]
pub extern "C" fn my_function(input: Vec2) {
println!("{}", input.x);
}
// Define our FFI interface as `ffi_inventory` containing
// a single function `my_function`. Types are inferred.
pub fn ffi_inventory() -> Inventory {
InventoryBuilder::new()
.register(function!(my_function))
.inventory()
}| Language | Crate | Sample Output1 |
|---|---|---|
| C# | interoptopus_backend_csharp | Interop.cs |
| C | interoptopus_backend_c | my_header.h |
| Python | interoptopus_backend_cpython | reference.py |
| Other | Write your own backend2 | - |
1 For the reference project.
2 Add support for a new language in just a few hours. No pull request needed. Pinkie promise.
If you want to ...
- create a new API see the hello world,
- understand what's possible, see the reference project,
- support a new language, copy the C backend.
See the reference project for an overview:
- functions (
extern "C"functions and delegates) - types (composites, enums, opaques, references, ...)
- constants (primitive constants; results of const evaluation)
- patterns (ASCII pointers, options, slices, classes, ...)
Generated low-level bindings are zero cost w.r.t. hand-crafted bindings for that language.
That said, even hand-crafted bindings encounter some target-specific overhead at the FFI boundary (e.g., marshalling or pinning in managed languages). For C# that cost is often nanoseconds, for Python CFFI it can be microseconds.
While ultimately there is nothing you can do about a language's FFI performance, being aware of call costs can help you design better APIs.
Detailed call cost tables can be found here: 🔥
For a quick overview, this table lists the most common call types in ns / call:
| Construct | C# | Python |
|---|---|---|
primitive_void() |
7 | 272 |
primitive_u32(0) |
8 | 392 |
many_args_5(0, 0, 0, 0, 0) |
10 | 786 |
callback(x => x, 0) |
43 | 1168 |
Gated behind feature flags, these enable:
derive- Proc macros such asffi_type, ...serde- Serde attributes on internal types.log- Invoke log on FFI errors.
- v0.14 - Better inventory UX.
- v0.13 - Python backend uses
ctypesnow. - v0.12 - Better compat using
#[ffi_service_method]. - v0.11 - C# switch ctors to static methods.
- v0.10 - C# flavors
DotNetandUnity(incl. Burst). - v0.9 - 150x faster C# slices, Python type hints.
- v0.8 - Moved testing functions to respective backends.
- v0.7 - Make patterns proc macros for better FFI docs.
- v0.6 - Renamed and clarified many patterns.
- v0.5 - More ergonomic slice usage in Rust and FFI.
- v0.4 - Enable logging support in auto-generated FFI calls.
- v0.3 - Better compatibility with generics.
- v0.2 - Introduced "patterns"; working interop for C#.
- v0.1 - First version.
Also see our upgrade instructions.
PRs are welcome.
- Submit small bug fixes directly. Major changes should be issues first.
- Anything that makes previously working bindings change behavior or stop compiling is a major change;
- This doesn't mean we're opposed to breaking stuff just that we'd like to talk about it before it happens.
- New features or patterns must be materialized in the reference project and accompanied by an interop test (i.e., a backend test running C# / Python against a DLL invoking that code) in at least one included backend.