memory-safety-patterns

To prevent use-after-free and memory leaks across C++ and Rust, apply RAII patterns and ownership semantics to bind resource lifetimes to object scopes, ensuring automatic cleanup and safe pointer access. This Skill provides cross-language guidance for implementing these safety mechanisms.

The best way to implement RAII for resource management in C++ is to wrap resources like file handles and mutexes in classes that acquire ownership during construction and automatically release them during destruction, ensuring safe resource handling and preventing leaks when scopes exit.

To translate C++ smart-pointer patterns into Rust ownership semantics, map reference-counted or uniquely owned pointers to Rust's strict ownership and borrowing rules, leveraging the compiler to enforce memory safety and prevent data races at compile time without manual tracking.

You can apply RAII-like resource guards in a C codebase by refactoring resource management routines to use scope-bound cleanup patterns and toolchain recommendations, helping manage container lifetimes and prevent leaks safely even without native object-oriented language features.

This approach helps with preventing data races in multi-language systems programming by applying consistent ownership and smart-pointer patterns across Rust, C++, and C, providing cross-language guidance to ensure correct resource handling and thread-safe API usage.