Algorithms, Ranges & Lambdas

What you'll walk away with

Explain the type, lifetime, and runtime behavior of Algorithms, Ranges & Lambdas
Use warnings and sanitizers to test failure cases
Write modern and safer C++

For Algorithms, Ranges & Lambdas, reason about container ownership, iterator and range validity, algorithm preconditions, and complexity together. Prefer standard algorithms and ranges over handwritten loops, with explicit mutation and allocation policies.

Build a Complete Mental Model

Apply It in Modern C++

Build an original Algorithms, Ranges & Lambdas example with `-std=c++23 -Wall -Wextra -Wpedantic` and test empty, boundary, invalid, and failure cases. Run lifetime-sensitive code under AddressSanitizer and UndefinedBehaviorSanitizer.

After This Lesson

Explain the ownership and lifetime contract
Build in C++23 mode with no warnings
Run a boundary or failure test under a sanitizer

cpp

#include <algorithm>
#include <iostream>
#include <vector>

int main() {
    std::vector values{5, 2, 8, 1};
    std::ranges::sort(values);
    for (int value : values) std::cout << value << ' ';
}

You should see

1 2 5 8

Try It Yourself

Memory and Safety Warning

Assuming one correct output proves lifetime, bounds, ownership, and undefined behavior are all correct.

The Current ISO C++ Standard (C++23) — Standard C++ Foundation

Easy traps

Assuming one correct output proves lifetime, bounds, ownership, and undefined behavior are all correct.
Assuming a raw pointer or iterator remains valid after its owning container or resource changes.

Hands-on Exercise

You'll know it worked when: 1 2 5 8