Include-what-you-use Alternatives

include-what-you-use reviews and mentions

• Open Source C++ Stack
  10 projects | dev.to | 16 Jul 2024

  Linters keep the code base consistent and help to catch a lot of issues and even bugs way before the compiler is ran. Clang-Tidy is the one I am relying on. IWYU is really helpful in keeping the includes clean, reducing number of dependencies and reducing the build times.

• IWYU: A tool for use with Clang to analyze includes in C and C++ source files
  1 project | news.ycombinator.com | 17 Nov 2023
• Script to find missing std includes in C++ headers
  1 project | news.ycombinator.com | 2 Oct 2023

  Interesting...how does it compare to https://github.com/include-what-you-use/include-what-you-use ?

• Speed Up C++ Compilation
  3 projects | news.ycombinator.com | 5 Aug 2023

  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?
  2 projects | /r/cpp_questions | 24 Jun 2023

  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 ?
  2 projects | /r/embedded | 19 Jun 2023

  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?
  2 projects | /r/cpp_questions | 3 May 2023

  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)!
  15 projects | /r/rust | 17 Apr 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
  4 projects | /r/programming | 23 Mar 2023
• IncludeGuardian - improve build times by removing expensive includes
  3 projects | /r/cpp | 21 Mar 2023

  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?

• A note from our sponsor - SaaSHub
  www.saashub.com | 15 Jan 2025

  SaaSHub helps you find the best software and product alternatives Learn more →