2 ms·
And you're running at least one static analysis tool and a linter on your C++ code too, right? You're not just deploying the C++ compiler output as-is, right?
by ttfkam 4y ago
And you're running at least one static analysis tool and a linter on your C++ code too, right? You're not just deploying the C++ compiler output as-is, right?
Those take time to run too and should absolutely be added to the compile time metrics when comparing against "cargo build".
- jesse__ 4y agoOn a personal project I run 2 metaprogramming passes, compile the entire project (~2m LoC) _twice_ and run the entire test suite in < 30s on a laptop from 2010. I don't run a linter because I hate them, and my metaprogramming passes do a bit of extra static checking clang doesn't. I occationally run extra static tools (valgrind et. al) but they're painfully slow and very rarely catch anything.
- kaba0 4y agoRust in incremental build mode is not slow at all, I really don’t see why people say so.