[cfe-dev] clang-tidy, clang-modernize, and remove-cstr-calls

[Richard]

Hi,

The description for clang-tidy[1] says:

    "clang-tidy is a clang-based C++ linter tool. Its purpose is to
    provide an extensible framework for diagnosing and fixing typical
    programming errors, like style violations, interface misuse, or
    bugs that can be deduced via static analysis. clang-tidy is
    modular and provides a convenient interface for writing new
    checks."

clang-tidy is a bit odd in that it can be used in either detection
mode (report problems like a standard lint tool) or "fix" mode
(refactor the problem away, which no lint tool ever did).

So the "remove void argument"[2] tool that I've been working on feels
like it fits in with clang-tidy.

My tool is very much patterned on remove-cstr-calls tool, which isn't
documented on the web site.

Should remove-cstr-calls be migrated to a clang-tidy check?

What about clang-modernize?  Are the transformations there considered
to be of the lint variety?  Should those transformations be migrated
to clang-tidy as well?

[1] <http://clang.llvm.org/extra/clang-tidy.html>
[2] <https://github.com/legalizeadulthood/remove-void-args>
-- 
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
     The Computer Graphics Museum <http://ComputerGraphicsMuseum.org>
         The Terminals Wiki <http://terminals.classiccmp.org>
  Legalize Adulthood! (my blog) <http://LegalizeAdulthood.wordpress.com>