m02-resource

Use Rc for single-threaded Rust resource management to enable shared ownership at low cost, whereas Arc provides thread-safe reference counting for multi-threaded environments. Rc fails to compile if sent across threads.

Prevent reference cycles in Rust smart pointers by using Weak references for parent or back-references. Weak references do not increment the strong reference count, allowing memory to be safely deallocated when the cycle breaks.

Handle interior mutability in Rust by combining smart pointers like RefCell or Mutex to enforce borrowing rules dynamically. This pattern allows mutating data through an immutable reference, ensuring safe resource management.

Rust uses Box for exclusive heap allocation when you need single ownership of a sized resource. Box provides straightforward heap allocation and ownership transfer with zero runtime overhead.

Select the right smart pointer for shared mutable state in Rust by combining Arc for thread-safe ownership with Mutex or RwLock for synchronized mutation. This pairing ensures safe concurrency and efficient resource management across threads.

Using Rc in a multi-threaded Rust application causes errors because Rc lacks atomic operations for thread-safe reference counting. Rust's compiler rejects this to prevent data races, requiring Arc for multi-threaded resource management.