Looks fine!

Any recipe to run the tests correctly would be nice :)

do you have commit rights ?

In D23680#524825, @nkosjar wrote:

Should this option consider the checks provided with "-checks="? That would be in line with clang-tidy and would allow IDEs to query the checks enabled by default (providing -meta-checks but no -checks=).

Honoring -checks= would also mean that available_categories in checks.json needs to be adapted accordingly. That is, this patch would not only dump the compiled in string, but read the json, and filter it.

In D23680#524517, @nkosjar wrote:

I'm not sure whether "-meta-checks" is descriptive enough. Can't come up with a better name right now. Suggestions?

How do I run the tests properly? I've tried running tests/run_tests.py from the build dir, but this results in many errors...

this landed, thanks!

Run ./dev-scripts/generate.py --generate (which reads the checks.json file)

pushed

needs a rebase, then it probably can be merged (if it's functionally equivalent, i.e. doesn't remove the env vars just yet)
then in another commit it can read from .clazy

I'll fix the docs, thanks

Actually these functions have been deprecated for 5.14.

some things are unrelated and so simple that should be committed directly already

Also, please edit checks.json, add your check there, with level "0", since it doesn't have false positives.

The preferred way is always to use one of the built-in clang warnings and make clazy spend less CPU cycles. I wonder why these are just not marked as deprecated.