Expose Rust types to C/C++ and WASM via Diplomat FFI bindings.
npx skills add https://github.com/novelsaga/NSaga --skill ffi-diplomat
Please help me install this Agent Skill. Skill: ffi-diplomat Source: https://github.com/novelsaga/NSaga/tree/main/.opencode/skills/ffi-diplomat Command: npx skills add https://github.com/novelsaga/NSaga --skill ffi-diplomat
Expose Rust types to C/C++ and WASM through a structured Diplomat FFI binding pattern. The approach reduces boilerplate and error-prone hand-written bindings across language boundaries.
Create a single #[diplomat::bridge] module that exposes the public Rust types to C/C++ and WASM.
High-intent search queries and answers about installing and using this skill.
You can expose Rust types to C/C++ and WASM using Diplomat to reduce boilerplate. It enforces a structured FFI binding pattern with a single #[diplomat::bridge] module and #[diplomat::opaque] wrappers to safely encapsulate internal types across language boundaries.
The best way to handle cross-language string IO is using DiplomatStr and DiplomatWrite. These mechanisms are part of the Diplomat FFI binding pattern, ensuring robust string handling when exposing Rust types to C/C++ and WASM environments.
To set up a Diplomat bridge, create a single #[diplomat::bridge] module that centralizes all FFI definitions. Within this module, apply #[diplomat::opaque] wrappers to your types and use constructor attributes to expose them to C/C++ and WASM.
Yes, you can use Diplomat to generate WASM bindings from Rust libraries. It specifically supports exposing Rust types to WASM alongside C/C++ by enforcing opaque wrappers and structured bridge modules, reducing hand-written binding errors.
You should use #[diplomat::opaque] wrappers because they safely encapsulate internal Rust types when exposing them to C/C++ and WASM. This prevents direct memory access across language boundaries, reducing boilerplate and avoiding error-prone hand-written FFI bindings.
No, the Diplomat FFI pattern enforces a single #[diplomat::bridge] module. All FFI definitions for exposing Rust types to both C/C++ and WASM are centralized in this one module, which reduces boilerplate and simplifies maintenance.
agentglassCreate WebAssembly bindings for TypeScript and JavaScript using Rust and wasm-bindgen.
RediSearchMap Rust FFI symbols to their C usage sites across the codebase.
balic-AI-ML-R-D-ResourcesIntegrate AddressSanitizer with fuzzing campaigns to detect memory safety bugs in C/C++ and Rust code.
vanyastaffProvide FFI guidelines for calling C from Rust and exposing Rust APIs.
