qt-creator VS include-what-you-use

Qt Creator is always a great option. Don’t let the name confuse you. Qt Creator has some advanced support for programming with the Qt framework, but it works just as well as a general C++ IDE.

qt-creator is a nice open-source IDE:

https://github.com/qt-creator/qt-creator

They offer binary releases, but it's also possible to compile from source without too much trouble. Written in C++, it's pretty snappy. Supports meson.

They ship a very solid bloat-free open source IDE called Qt Creator, built specifically for development with Qt, that comes complete with a GUI designer, built-in Qt tutorials, and example projects, among other things. I use it as a daily driver for all of my C++ projects (even non-Qt projects), as it strikes a good balance between being simple, responsive, and to the point, while still having many useful tools and features.

There is no picture to show... GitHub page I'm reading is here: https://github.com/qt-creator/qt-creator

Qt Creator is a great C/C++ editor

Qt Creator (link to source) is written with C++.

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.