"Oh no... that value changed unexpectedly. That's probably... A memory leak. I'm gonna have to recompile with... *gulp*... The address sanitizer."
*intense grinding noises*
Seriously, I don't know if this is an our-codebase problem or a general C++ problem, but I generally use three configs: debug symbols, production-optimized, and address sanitizer.
We use Bazel as our build management system, and changing configs is a "go get coffee" change. Ten to twenty minute recompiles.
@mtomczak with Bazel and a distributed build cache it should be quite fast, especially if your CI builds all three variants.
@bhollis I'm going to have to bring myself up to speed on this feature. Our CI is in a bit of a state right now, but if I can learn how to set up a distributed build cache I'll look into donating time to the build team to make it happen.
