Scripting & runtime · native FFI

Call explicitly typed C ABI functions.

The v4.5 FFI opens a native library, resolves a symbol, and calls it through a signature you provide. It is an unsafe typed boundary—not automatic C header or ABI inference.

lib := ffi_open("./libmath_helpers.so")
sum := ffi_call(lib, "add_i64", "i64(i64,i64)", 20, 22)
print(sum)
ffi_close(lib)

Use .so on Linux, .dylib on macOS, and .dll on Windows. Keep the library open for every call and callback that depends on it; calling through a closed handle is an error.

Supported boundary

Signatures cover the maintained scalar integer, floating-point, boolean, C-string, pointer and void forms, plus explicit null pointers. Nift-owned native buffers and declared struct layouts provide bounded memory exchange without pretending arbitrary C layouts are self-describing. Unsupported signatures, layouts, calling conventions, argument counts, conversions, or missing symbols fail explicitly.

Callbacks and lifetime

Callbacks are bounded synchronous calls from native code into a Nift callable. Keep the callback and its owning runtime alive for the entire native call. Native code must not retain the callback for later or invoke it asynchronously after ffi_call returns. Callback failures cross the boundary as controlled runtime errors rather than exceptions escaping through C.