rust-smart-pointers

Fix Rust smart-pointer issues by analyzing codebases for anti-patterns with Box, Rc, Arc, and RefCell, then applying recommended type substitutions and refactoring guidelines to prevent leaks and panics.

Avoid Rc and RefCell reference cycles by using Weak references to break strong count loops, applying static analysis to detect interior mutability anti-patterns, and substituting safer pointer types for single-thread contexts.

Choose between Arc<Mutex> and Arc<RwLock> by evaluating thread-safety trade-offs, detecting Arc misuse in multi-thread contexts, and applying best-practice guidelines for concurrent access patterns in Rust.

Detect Box misuse for large recursive data structures by running static analysis on Rust codebases to flag inappropriate indirection and suggest correct smart-pointer alternatives.

Common RefCell borrow-check pitfalls include runtime panics from overlapping mutable borrows, resolvable by identifying interior mutability anti-patterns and providing safe alternatives through static code analysis.

Do not use Rc in multi-threaded Rust applications because it lacks thread safety, resolvable by flagging Rc misuse in multi-thread contexts and recommending Arc substitutions for safe concurrent access.