include-what-you-use
A tool for use with clang to analyze #includes in C and C++ source files (by include-what-you-use)
OCLint
A static source code analysis tool to improve quality and reduce defects for C, C++ and Objective-C (by oclint)
Our great sponsors
include-what-you-use | OCLint | |
---|---|---|
39 | 1 | |
3,819 | 3,717 | |
2.4% | 0.0% | |
9.4 | 0.0 | |
5 days ago | almost 2 years ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
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.
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.
OCLint
Posts with mentions or reviews of OCLint.
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
and five C/C++ static code analyzers: * clang-tidy * oclint * cppcheck * cpplint (recently added!) * include-what-you-use (recently added!)
What are some alternatives?
When comparing include-what-you-use and OCLint you can also consider the following projects:
cppinclude - Tool for analyzing includes in C++
SwiftLint - A tool to enforce Swift style and conventions.
coc-clangd - clangd extension for coc.nvim
Tailor - Cross-platform static analyzer and linter for Swift.
cpplint - Static code checker for C++
SwiftCop - SwiftCop is a validation library fully written in Swift and inspired by the clarity of Ruby On Rails Active Record validations.
clangd - clangd language server
ocstyle - Objective-C style checker
Cppcheck - static analysis of C/C++ code
SwiftFormat - A command-line tool and Xcode Extension for formatting Swift code
uncrustify - Code beautifier
include-what-you-use vs cppinclude
OCLint vs SwiftLint
include-what-you-use vs coc-clangd
OCLint vs Tailor
include-what-you-use vs cpplint
OCLint vs SwiftCop
include-what-you-use vs clangd
OCLint vs ocstyle
include-what-you-use vs Cppcheck
OCLint vs SwiftFormat
include-what-you-use vs uncrustify
OCLint vs cpplint