m01-ownership

To decide between std::unique_ptr and std::shared_ptr for C++ ownership, use unique_ptr for exclusive ownership and shared_ptr when multiple parts of your codebase need shared access. This skill guides proper RAII selection.

The best way to avoid use-after-free and double free errors in C++ is by applying RAII and move semantics with smart pointers. This skill provides guidance on clear lifetime management to prevent these common defects.

RAII ensures memory safety in C++ by binding resource lifetimes to object scopes, automatically releasing resources when objects go out of scope. This skill helps standardize ownership patterns using stack objects and smart pointers.

Use raw pointers and non-owning references in C++ when you need to observe or access an object without taking ownership. This skill guides correct usage of non-owning references alongside std::unique_ptr and std::shared_ptr.

Yes, this guidance applies to large C++ codebases. It covers real-world scenarios spanning small utilities to large codebases, helping standardize ownership patterns and resource management strategies across varying project scales.

Transferring ownership with move semantics prevents memory leaks by ensuring a single owner takes responsibility for the resource at any given time without copying. This skill guides correct move semantics application to avoid leaks.