Browse all 9 articles in this open-source series. Nine source-grounded C++ lessons on fmt: formatting contracts, CMake integration, type erasure, buffer limits, argument ownership and measurement. Full multilingual revision of the retained series.
Featured starting point
Understand fmt through its actual C++ APIs: typed formatting, output destinations, header organization and the difference between compile-time checks and compiled format strings.
Suggested learning path
01 → 09
Understand fmt through its actual C++ APIs: typed formatting, output destinations, header organization and the difference between compile-time checks and compiled format strings.
Build a minimal C++20 example, distinguish literal and runtime errors, and extend a domain type with format_as without writing a new parser.
Treat fmt deployment as a dependency and ABI decision. Pin the source, select one CMake target and distinguish a local header-only probe from a production build matrix.
Trace fmt::format through a checked front end into vformat and its buffer, then examine how argument views and dynamic storage change lifetime obligations.
Read the bounded-output traits and upstream tests to understand total size, the returned iterator, missing null termination and UTF-8 byte truncation.
Inspect the 500-element inline buffer and growth policy, separate format checking from FMT_COMPILE, and measure formatting, allocation, I/O and build costs independently.
Distinguish untrusted text from a runtime format program, preserve borrowed data lifetimes, and avoid mistaking type safety or bounded writes for complete output security.
Choose a formatting dependency by required presentation, toolchain support, ownership and maintenance—not an unverified claim that one library is fastest everywhere.
Design a small educational explorer for format contracts and buffer limits, with explicit expected results and no claim that an interactive demo or official roadmap is already shipped.
