std::transform has been the standard library’s go-to “apply a function to every element of a sequence” tool since C++98. It works. It’s also showing every one of its twenty-five-plus years: callers spell out begin() and end() for every range, ad-hoc projections require an extra lambda…
A scene with a thousand trees of the same model has a problem the naive engine doesn’t notice: each Tree instance owns its own copy of the same vertex data, the same index data, and issues its own draw call against them.…
The need to return or pass several values of different types comes up often enough that almost every C++ programmer has, at some point, written a one-off struct just to bundle them together. std::tuple is the generic answer to that recurring problem: a fixed-size sequence of…
The typename keyword has two jobs in C++ that look unrelated until you recognise they’re the same job at different depths. The familiar use is in template parameter lists — template <typename T> — where it announces a type parameter. The trickier use is…
std::unexpected_handler is one of the most thoroughly removed features in the C++ standard library — deprecated in C++11, gone entirely from the standard in C++17, and the name itself recycled in C++23 for an unrelated purpose (it now lives on as…
The mental model most C++ programmers carry is that calling a function pushes its arguments onto the stack — a stack frame appears, parameters live in it, the callee reads them from known offsets. That picture was largely accurate in…
The STL algorithms have a quietly subtle rule about the function objects you pass them. Read the standard literally and you’d think std::transform and friends require completely side-effect-free function objects — no modifying any variable, no I/O, no temporaries. Read the standard as…
C++ has had two different mechanisms for declaring “this function won’t throw” — the old throw(…) exception specification and the modern noexcept specifier — and they enforce that promise in radically different ways. The old mechanism checked at runtime: if a forbidden exception escaped,…
C++ inherited an ugly tradition from C: when a function needs to operate on a sequence of values, it takes a pointer and a size as separate parameters. The pointer is typed; the size is just a number; nothing in…
The intuitive way to write a game loop is the wrong one. Sample how much time has passed since the last frame, hand that delta to the physics step, render, repeat. This works visually for the same reason it fails…