For this reason, we considered adding this functionality to the LibTooling component. However, this would also introduce LibTooling as a dependency of the Clang binary, since the Static Analyzer is the part of Clang.
I run some quick benchmarks about the binary size (using static linking on Linux).
Release: 85457072 -> 85505864
Debug: 1777932672 -> 1779938696
The increase is about 0,1% in the worst case. This can also mean slightly increased link times and the clang binary needs to be recompiled when there is a tooling related change.
The question is, is it ok for the community to have this dependency or should we introduce a new component instead of putting this functionality in LibTooling?