This is an archive of the discontinued LLVM Phabricator instance.

Refactor: Organize module per-check files into subdirectories for each module
AbandonedPublic

Authored by LegalizeAdulthood on Mar 2 2015, 3:16 AM.

Details

Reviewers
alexfh
Summary

The test/clang-tidy directory is getting crowded. Move the module per-check source files into module subdirectories.

Diff Detail

Event Timeline

LegalizeAdulthood retitled this revision from to Refactor: Organize module per-check files into subdirectories for each module.
LegalizeAdulthood updated this object.
LegalizeAdulthood edited the test plan for this revision. (Show Details)
LegalizeAdulthood added a reviewer: alexfh.
LegalizeAdulthood added a subscriber: Unknown Object (MLST).
alexfh edited edge metadata.Mar 2 2015, 7:00 AM

I'm not sure we need this, but even if we do, I'd better not remove the module names from the file names, e.g. test/clang-tidy/google/google-readability-casting.cpp, etc. Also, the contents of the Inputs directory would need to be distributed to appropriate subdirectories.

But again, I currently don't see the benefit of moving the tests.

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?

LegalizeAdulthood abandoned this revision.Mar 4 2015, 10:16 AM

Abandoning this as per Alexander's comments.

test/clang-tidy/readability-redundant-smartptr-get.cpp