Smart Pointers in Modern C++

Smart Pointers: Modern C++ Memory Management

Smart pointers were introduced in C++11 to provide automatic memory management while maintaining the performance characteristics of C++. They use RAII to ensure proper resource cleanup and eliminate most memory-related bugs.

The Three Smart Pointers

1. std::unique_ptr: Exclusive ownership
2. std::shared_ptr: Shared ownership with reference counting
3. std::weak_ptr: Non-owning observation

// Creating unique_ptr
auto ptr = std::make_unique<Widget>(args);

// Transfer ownership
auto ptr2 = std::move(ptr);  // ptr is now nullptr

// Automatic cleanup when out of scope
{
    auto local = std::make_unique<Resource>();
} // Resource destroyed here

// Custom deleter
auto file = std::unique_ptr<FILE, decltype(&fclose)>(
    fopen("data.txt", "r"), &fclose
);

auto ptr1 = std::make_unique<Widget>();

Unique Pointer (std::unique_ptr)

Characteristics

• Exclusive ownership: Only one unique_ptr can own a resource
• Move semantics: Ownership can be transferred but not copied
• Zero overhead: Same performance as raw pointers
• Custom deleters: Support for custom cleanup functions

Usage Examples

// Creating unique_ptr
auto ptr = std::make_unique<Widget>(args);

// Transfer ownership
auto ptr2 = std::move(ptr);  // ptr becomes nullptr

// Custom deleter
auto file = std::unique_ptr<FILE, decltype(&fclose)>(
    fopen("data.txt", "r"), &fclose
);

Shared Pointer (std::shared_ptr)

Characteristics

• Shared ownership: Multiple pointers can own the same resource
• Reference counting: Tracks how many pointers reference the object
• Thread-safe counting: Reference count operations are atomic
• Automatic cleanup: Object deleted when count reaches zero

Reference Counting Process

1. Create shared_ptr → count = 1
2. Copy shared_ptr → count increments
3. Destroy shared_ptr → count decrements
4. Count reaches 0 → object deleted

Circular Reference Problem

struct Node {
    std::shared_ptr<Node> next;
    std::weak_ptr<Node> parent;  // Break cycle with weak_ptr
};

Weak Pointer (std::weak_ptr)

Characteristics

• Non-owning: Doesn't affect reference count
• Observer pattern: Safely observe shared_ptr objects
• Cycle breaking: Prevents circular references
• Expiration checking: Can detect if object still exists

Usage Pattern

std::shared_ptr<Widget> shared = std::make_shared<Widget>();
std::weak_ptr<Widget> weak = shared;

if (auto locked = weak.lock()) {
    // Use locked as shared_ptr
    locked->doSomething();
} else {
    // Object was destroyed
}

Best Practices

1. Prefer make_unique and make_shared for creation
2. Use unique_ptr by default, shared_ptr when sharing needed
3. Pass raw pointers to functions that don't affect ownership
4. Return smart pointers from factory functions
5. Use custom deleters for non-standard cleanup

Performance Considerations

• unique_ptr: Zero overhead compared to raw pointers
• shared_ptr: Small overhead for reference counting
• weak_ptr: Minimal overhead, but requires lock() to access
• make_shared: More efficient than shared_ptr(new T())

Smart pointers represent modern C++'s answer to memory management - providing safety without sacrificing performance.

Related concepts