FFI and Interoperability — Senior¶

Version native libraries, test ABI compatibility, and isolate unsafe code. Define cancellation and asynchronous completion ownership. Use sanitizers, fuzzers, crash symbols, and cross-language contract tests. Prefer process or RPC isolation when memory corruption blast radius is unacceptable.

Test yourself¶

1. How do you roll out an ABI-breaking change?
2. Who owns an async buffer after cancellation?
3. When is RPC safer than in-process FFI?

Continue to professional.md.