|
|
|
|
|
by ttfkam
1460 days 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". |
|
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.