Bug 407258

Summary:	clazy-standalone/clang-tidy substitution
Product:	[Developer tools] clazy	Reporter:	Christian Gagneraud <chgans>
Component:	general	Assignee:	Christian Gagneraud <chgans>
Status:	REPORTED ---
Severity:	normal	CC:	nikolai.kosjar, smartins
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description Christian Gagneraud 2019-05-06 03:28:20 UTC

SUMMARY

Currently there are cases where clazy-standalone cannot be substituted to clang-tidy.

To make clazy-standalone command-line options par with clang-tidy, there is a need for:
 - Support for filter selection (eg, using `-` and `*`)
 - Support for config file [1]
 - Support for listing

[1] at least these properties:
 - Checks
 - WarningsAsErrors
 - HeaderFilterRegex


I haven't look at clang-tidy code, but it doesn't seem to be something over-complicated. Will investigate and report.

Comment 1 Nikolai Kosjar 2019-07-19 09:57:28 UTC

Somewhat related: https://bugs.kde.org/show_bug.cgi?id=409986

Comment 2 Christian Gagneraud 2020-09-30 22:21:12 UTC

Hi,

Is there any plan to merge clazy in clang-tidy?

I don't have any plan to work on the issue #407258 unfortunately.

As a user of both tools, i find clang-tidy to be easier to use and integrate (eg CI), for example run-clang-tidy allows to run checks in parallel, something that not even clazy-standalone provides.

IMHO, merging clazy in clang-tidy would make the user happier and will lessen the maintenance and improvement (catching up with clang-tid) burden.

Chris

Comment 3 Sergio Martins 2020-10-04 23:09:25 UTC

There's no plans for merging them, and that would take a lot of work.
Our best bet would be clang-tidy supporting plugins. There's been some talk about this in the llvm mailing lists, not sure what's the status there.