Generate safe Rust FFI bindings with ownership and panic containment.
npx skills add https://github.com/cecon123/tg-remote-bot --skill rust-ffi-cecon123
Please help me install this Agent Skill. Skill: rust-ffi Source: https://github.com/cecon123/tg-remote-bot/tree/main/.agents/skills/rust-ffi Command: npx skills add https://github.com/cecon123/tg-remote-bot --skill rust-ffi-cecon123
FFI between Rust and C/C++ often leaks memory, risks panics crossing boundaries, and makes ownership transfer unclear. This skill provides proven patterns and tooling guidance to keep cross-language calls safe, predictable, and maintainable.
Ask the AI to generate safe Rust-C FFI bindings for a given C header and verify memory ownership boundaries.
High-intent search queries and answers about installing and using this skill.
Prevent memory leaks in Rust-C FFI bindings by defining clear ownership contracts with paired create and free functions, ensuring explicit memory lifecycle management across the language boundary to keep cross-language calls predictable.
The safest way to handle Rust panics crossing the C FFI boundary is through panic containment, which catches panics before they cross into C code to prevent undefined behavior and maintain stable application execution.
Use bindgen to generate Rust bindings from C headers and cbindgen to generate C headers from Rust, ensuring stable ABIs through explicit extern "C" interfaces and #[repr(C)] data layouts for safe interoperability.
Yes, Rust FFI patterns support Python and Java interop by providing binding generation guidance using PyO3 for Python and JNI for Java, extending safe cross-language data type mapping and error handling to higher-level languages.
To verify memory ownership boundaries in Rust FFI, define explicit data type mapping and paired allocation functions, ensuring the foreign language only frees memory allocated by its corresponding boundary partner to prevent undefined behavior.
Rust FFI code causes undefined behavior across language boundaries due to uncontained panics, mismatched data layouts without #[repr(C)], or unclear memory ownership, which robust FFI patterns resolve through explicit error handling and lifecycle contracts.
yash-gargCompiles C/C++ code into Dart Native Assets using build and link hooks.
rsmdtPlan staged code refactorings with baseline tests and behavior preservation.
bahayonghangDiagnose slow Rust and Cargo builds using cargo --timings and linker analysis.
Sumeet138Apply RAII, ownership, and smart pointer patterns for memory safety in C, C++, and Rust.
