[PATCH] Refactor: Organize module per-check files into subdirectories for each module

Richard legalize at xmission.com
Mon Mar 2 10:39:31 PST 2015


My motivation is as stated: this directory is getting crowded with files and the more checks we add, the more crowded it is going to get.

It also makes it clear which test files are associated with a specific check (because they are in the subdir for the module) and which are testing basic functionality of clang-tidy itself (like `basic.cpp`).

Once the files are moved into a subdirectory per-module, then having the module name in the test file is redundant and no longer needed.  What is to be gained from repeating it in the filename when it is grouped into a subdirectory for the module?


http://reviews.llvm.org/D8000

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/






More information about the cfe-commits mailing list