Details
- Reviewers
alexfh hokein aaron.ballman
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Unit tests: pass. 60968 tests passed, 0 failed and 727 were skipped.
clang-tidy: fail. Please fix clang-tidy findings.
clang-format: fail. Please format your changes with clang-format by running git-clang-format HEAD^ or applying this patch.
Build artifacts: diff.json, clang-tidy.txt, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
Where set of Clang-tidy checks come from? .clang-tidy? Could stricter set of custom rules be used?
clang/include/clang/Analysis/AnalysisDeclContext.h | ||
---|---|---|
527 | Shouldn't absence of comment for closing #endif detected by Clang-tidy? |
Yes, clang-tidy uses the .clang-tidy. Do you want to enable additional rules for a subproject?
It really depends on state of each project. There are a lot of legacy issues, but it makes sense to treat new code with more demands, for example with respect to modernize checks.
What version of clang-tidy and clang-format does this run? Whatever is available in Debian packages?
clang-tidy: warning: header guard does not follow preferred style [llvm-header-guard]