tl;dr: Results! IntroBaseline Compile TimesReducing Include CostIdentifying Compilation CostIt’s a Problem of ScaleForward DeclarationDetermining What’s ExpensiveDeduplicating Duplicitous DuplicationEnter The DragonThe Final Code?Results!Oddities, Errors, and Errata Intro Templates are one of the most ubiquitous features of C++, allowing programmers to write
C++ Compilation: Fixing It
For fixing compile times, there is no magic bullet. It takes work and work takes time. Before you spend time reducing compile (and link) times, evaluate if it actually makes sense. If you spend more on making the changes than
C++ Compilation: Lies, Damned Lies, and Statistics
no, seriously, tl;dr… How the Test Works Optimizing the Test Reasonable Confidence Bias TL;DR Results by Compiler Results by C++ Standard Visual Studio 2015 Visual Studio 2017 clang 7.0.1 Heuristics In the first post, C++ Headers Are Expensive!, I posted
C++ Compilation: What’s Slowing Us Down?
The last post on how long it takes to include (not even use) and compile the standard C/C++ headers left a whole lot of people like: There were questions like “What about using an SSD?” “What about the file cache?”