@@ -335,7 +335,7 @@ Clang-Tidy Automation
335335=====================
336336
337337:program: `clang-tidy ` can analyze multiple source files by specifying them on the
338- command line or by using a compilation database . For larger projects, automation
338+ command line. For larger projects, automation
339339scripts provide additional functionality like parallel execution and integration
340340with version control systems.
341341
@@ -346,7 +346,7 @@ Running Clang-Tidy in Parallel
346346with many source files, the :program: `run-clang-tidy.py ` script provides parallel
347347execution to significantly reduce analysis time. This script is included with
348348clang-tidy and runs :program: `clang-tidy ` over all files in a compilation database
349- concurrently.
349+ or a specified path concurrently.
350350
351351The script requires a compilation database (``compile_commands.json ``) which can
352352be generated by build systems like CMake (using ``-DCMAKE_EXPORT_COMPILE_COMMANDS=ON ``)
@@ -379,10 +379,8 @@ The :program:`clang-tidy-diff.py` script allows you to run :program:`clang-tidy`
379379on the lines that have been modified in your working directory or in a
380380specific diff. Importantly, clang-tidy-diff only reports diagnostics for changed
381381lines; :program: `clang-tidy ` still analyzes the entire file and filters out
382- unchanged lines after analysis, so this does not improve performance. The script
383- is essentially a wrapper that parses diff output and passes it to
384- :program: `clang-tidy ` with the ``--line-filter `` option, which performs all the
385- actual filtering. This is particularly useful for code reviews and continuous
382+ unchanged lines after analysis, so this does not improve performance. This is
383+ particularly useful for code reviews and continuous
386384integration, as it focuses analysis on the changed code rather than the entire
387385codebase.
388386
0 commit comments