Why the FFI boundary is useful
Native host applications use different languages, frameworks and release cycles. A deliberately small C-compatible boundary can act as a language-neutral hand-off point while internal Rust types remain private implementation detail.
What an integrator needs to know
- Which API/ABI version belongs to the reviewed release?
- Which state belongs to the host and which remains inside the runtime?
- How are errors, cancellation, shutdown and updates represented?
- Which target platforms and bindings are verified for the specific release?
What this page explicitly does not claim: Rust and FFI are technology and integration anchors. They do not imply absolute memory-safety guarantees, a specific performance level, universal platform coverage or production status.