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.

Maybe rename to -supported-checks-json , doesn't matter if it's too long, it's for IDE consumption only.
And, as the name suggests, it will print all supported checks.

Something that honours -checks can be orthogonal and be in another option. Also note that the CLAZY_CHECKS env var also influences the checks that are used.
Does this second option even need to be json based ? it can just output the list of enabled checks, and then you can cross-reference with the json you already have

Tue, Sep 3

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=).