[Clang Tidy][Efficiency] Clang tidy wastes endless time on checking non-usercode

[hasselmm]

• Actual behavior: Clang Tidy searches for errors in non-user code.
• Expected behavior: Clang Tidy only does the abolut minimum when processing non-user code for efficency

Clang Tidy is slow. Very slow. So actually it's very surprising to read such messages:

Suppressed 48487 warnings (48482 in non-user code, 5 NOLINT)

So Clang Tidy tells me proudly it has wasted endless time on identifying 48.487 errors in non-user code. Code I am most likely never every going to fix. Code that I most likely can't even fix without causing serious problem. This is bizzare, to put it nicely.

Efficency is key to make using Clang Tidy a no-brainer, a mandatory task in C++ programming. Therefore Clang Tidy should spend as little time as possible on non-user code. It should just skip non-user code without even trying to analyse it for flaws.

[vbvictor]

Duplicate of #52959.
Work was done in pr, but had to be reverted due to appeared issues.
Hopefully it will reland in the near future.

[llvmbot]

@llvm/issue-subscribers-clang-tidy

Author: Mathias Hasselmann (hasselmm)

* Actual behavior: Clang Tidy searches for errors in non-user code. * Expected behavior: Clang Tidy only does the abolut minimum when processing non-user code for efficency

Clang Tidy is slow. Very slow. So actually it's very surprising to read such messages:

Suppressed 48487 warnings (48482 in non-user code, 5 NOLINT)

So Clang Tidy tells me proudly it has wasted endless time on identifying 48.487 errors in non-user code. Code I am most likely never every going to fix. Code that I most likely can't even fix without causing serious problem. This is bizzare, to put it nicely.

Efficency is key to make using Clang Tidy a no-brainer, a mandatory task in C++ programming. Therefore Clang Tidy should spend as little time as possible on non-user code. It should just skip non-user code without even trying to analyse it for flaws.