pre-commit-hooks
C/C++ hooks to integrate with pre-commit (by pocc)
include-what-you-use
A tool for use with clang to analyze #includes in C and C++ source files (by include-what-you-use)
pre-commit-hooks | include-what-you-use | |
---|---|---|
1 | 39 | |
289 | 3,877 | |
- | 2.7% | |
0.0 | 9.4 | |
about 1 month ago | 1 day ago | |
Python | C++ | |
Apache License 2.0 | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pre-commit-hooks
Posts with mentions or reviews of pre-commit-hooks.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-13.
-
C/C++ pre-commit hooks for static analyzers and linters
I maintain pre-commit hooks for C/C++ linters and static analyzers using the pre-commit framework. These allow you to verify that your code is free of common errors and to format it consistently. Included are
include-what-you-use
Posts with mentions or reviews of include-what-you-use.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-05.
- IWYU: A tool for use with Clang to analyze includes in C and C++ source files
-
Script to find missing std includes in C++ headers
Interesting...how does it compare to https://github.com/include-what-you-use/include-what-you-use ?
-
Speed Up C++ Compilation
Build Insights in Visual Studio, include-what-you-use).
Looks like https://include-what-you-use.org/ might do that.
-
Is it good or bad practice to include headers that are indirectly included from other headers?
If you are worried about includes, use https://github.com/include-what-you-use/include-what-you-use and stop thinking about it.
-
how do you guys manage a include file mess ?
Getting rid of that is not straightforard, though some tools can help with that
-
Is it appropiate to comment what a header is needed for?
You can use the tool https://github.com/include-what-you-use/include-what-you-use to do this for for. It tracks included files and can give comment for what is used from each file. It also warns you when you include files that you don’t use
-
Hey Rustaceans! Got a question? Ask here (16/2023)!
Invisible imports (e.g. traits). In Python, everything is fully namespaced (unless you from import * in which case all bets are off). It's always explicit where a name is coming from. C is the opposite: #include lets you refer to anything defined in the headers with no namespacing. That's why a common strategy (include what you use) has an associated code style: after every non-std #include you have a comment saying which of its definitions you are using. Of course, Rust is much less implicit, but I still sometimes struggle with traits. For example, you can use tokio::net::TcpStream, but you need to also use tokio::io::AsyncReadExt for the .read trait to be defined on TcpStream. This makes it hard (for me) to answer questions like "what traits are currently available in this scope?" and "why is this module being imported?"
- I implemented a NASA image compression algorithm
-
IncludeGuardian - improve build times by removing expensive includes
Aside from being closed source and not available on all architectures, how does it compare to iwyu(https://include-what-you-use.org/) or clang's relatively recent include-fixer which is also accessible via clangd?
-
Do you include standard library headers in your implementation file, if they're already been included in the corresponding header file?
I set up include-what-you-use and I let it tell me which headers should be where. The IWYU rules would have put all needed headers including in the cpp file.
What are some alternatives?
When comparing pre-commit-hooks and include-what-you-use you can also consider the following projects:
cpp-linter-action - A Github Action for linting C/C++ code integrating clang-tidy and clang-format to collect feedback provided in the form of file-annotations, thread-comments, workflow step-summary, and Pull Request reviews.
cppinclude - Tool for analyzing includes in C++
cmake-lint - Fork of https://github.com/richq/cmake-lint to continue maintenance
coc-clangd - clangd extension for coc.nvim
Cppcheck - static analysis of C/C++ code
cpplint - Static code checker for C++
OCLint - A static source code analysis tool to improve quality and reduce defects for C, C++ and Objective-C
clangd - clangd language server
uncrustify - Code beautifier
pre-commit-hooks vs cpp-linter-action
include-what-you-use vs cppinclude
pre-commit-hooks vs cmake-lint
include-what-you-use vs coc-clangd
pre-commit-hooks vs Cppcheck
include-what-you-use vs cpplint
pre-commit-hooks vs OCLint
include-what-you-use vs clangd
pre-commit-hooks vs cpplint
include-what-you-use vs Cppcheck
pre-commit-hooks vs uncrustify
include-what-you-use vs uncrustify