uncrustify VS include-what-you-use

these two C/C++ code formatters: * clang-format * uncrustify

Uncrustify

cd ~ git clone https://github.com/uncrustify/uncrustify.git

Build Insights in Visual Studio, include-what-you-use).

Looks like https://include-what-you-use.org/ might do that.

If you are worried about includes, use https://github.com/include-what-you-use/include-what-you-use and stop thinking about it.

Take a look at https://include-what-you-use.org/ . It sorts out the issue of what to include and where.

Getting rid of that is not straightforard, though some tools can help with that

I just recently heard of a tool Include What You Use that is an automation tool to help determine which include files you need and doesn't include files you dont.

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

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?"

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?

IWYU will look at the content of your sources and highlight include directives that it believes are unnecessary (and vice versa, recommend including files that you transitively depend on).