Select Rust ownership patterns and smart pointers for memory-safe data structures.
npx skills add https://github.com/simorgh3196/tsuzulint --skill m02-resource
Please help me install this Agent Skill. Skill: m02-resource Source: https://github.com/simorgh3196/tsuzulint/tree/main/.agents/skills/m02-resource Command: npx skills add https://github.com/simorgh3196/tsuzulint --skill m02-resource
This Skill guides Rust developers in selecting correct ownership patterns and smart pointers to manage memory safely and efficiently, reducing leaks and data races.
Ask for a recommended ownership pattern for a Rust struct, e.g.: "What pointer type should I use for a graph node with potential cycles?"
High-intent search queries and answers about installing and using this skill.
Use Rc for single-threaded shared ownership and Arc for multi-threaded contexts. Rc avoids atomic overhead in single-threaded programs, while Arc ensures safe concurrency across threads.
Prevent memory leaks in Rust cyclic graphs by pairing Rc or Arc with Weak references. Weak references break strong reference cycles, allowing nodes to be dropped cleanly without causing leaks.
Choose a Rust smart pointer by evaluating ownership and threading needs: Box for exclusive heap allocation, Rc or Arc for shared ownership, and RefCell or Cell for interior mutability.
Use RefCell for runtime-checked mutable borrows and Cell for Copy types requiring compile-timechecked interior mutability. They enable mutation within immutable structures, preventing data races safely.
Rust requires Box to define recursive data structures because it provides compile-time-known heap allocation size. Without Box, the compiler cannot determine the memory layout of self-referential types.
Yes, use Arc for thread-safe reference counting combined with Mutex or RwLock for safe concurrent access. This combination ensures memory safety and prevents data races in multi-threaded shared state.
CallMeLuigiv2Guide Rust memory management decisions across Box, Rc, Arc, Weak, RefCell, Cell ownership patterns.
mohitmishra786Validate Rust code for memory safety and undefined behavior with Miri.
JylhisRecommend Rust pointer/resource choices based on ownership and concurrency.
gregoryraymondDiagnose Rust borrow-checker errors and identify root causes.
