cpplint
include-what-you-use
Our great sponsors
cpplint | include-what-you-use | |
---|---|---|
2 | 39 | |
1,462 | 3,819 | |
2.3% | 2.4% | |
8.6 | 9.4 | |
4 days ago | 4 days ago | |
Python | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
cpplint
-
Configuring Cppcheck, Cpplint, and JSON Lint
I was configuring them as I was reading. I have done this before, but we had some months of use since then, and I have seen it working in real-time. I got a lot out of this second read and configuration round. I discovered that I over-configured Cppcheck; there is much more to get out of Cpplint, and I reviewed the JSON Schema versions.
-
C/C++ pre-commit hooks for static analyzers and linters
and five C/C++ static code analyzers: * clang-tidy * oclint * cppcheck * cpplint (recently added!) * include-what-you-use (recently added!)
include-what-you-use
- 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?
Cppcheck - static analysis of C/C++ code
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
uncrustify - Code beautifier
clangd - clangd language server
OCLint - A static source code analysis tool to improve quality and reduce defects for C, C++ and Objective-C
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.
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.