vim-clang-format VS include-what-you-use

OP you can use something like Clang Format to format your code (I believe the Microsoft C/C++ extension for VSCode comes with it, not sure tho)

you can give it a try to clang-format: https://clang.llvm.org/docs/ClangFormat.html

What you want is to use clang-format.

clang-format (https://clang.llvm.org/docs/ClangFormat.html) stop formatting your code manually - it is not your beautiful snowflake.

You can also give clang format a list of regular expressions to sort the includes in a particular order if that's what you need https://clang.llvm.org/docs/ClangFormatStyleOptions.html#includecategories

Maybe use clang-format to reformat your code https://clang.llvm.org/docs/ClangFormat.html

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

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.

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

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?

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.