A lot of this tooling is available for C++ development at Google.
Includes are added automatically when you use code completion. There is also a simple IDE command to add all the include dependencies to your build file.
I don't know how well rust is integrated with Googles internal tooling.
The golang integration is incredible, though. You don't need to touch includes or build dependencies at all. They are fully automated.
>A lot of this tooling is available for C++ development at Google.
No, it isn't. Google even has their own build system, because obviously CMake is so bad, but it it is made for insanely large systems not ease of entry for medium/small projects.
C++ slowly is adopting the language features that allow for such integrated tooling, but it isn't there yet. But right now the tooling can't exists simply because of what C++ is. The problems you can't easily solve in C++ are things like "how do I integrate this already existing library into our build chain", that is a legitimately hard question and millions of lines of code have been written trying to solve that problem.
There is no equivalent to cargo for C++, there is build2, there is conan there is vspkg and the VS build system. ALL of them suck and have their own gigantic problems which will raise their head and suddenly you are struggling with include and build problems.
Includes are added automatically when you use code completion. There is also a simple IDE command to add all the include dependencies to your build file.
I don't know how well rust is integrated with Googles internal tooling.
The golang integration is incredible, though. You don't need to touch includes or build dependencies at all. They are fully automated.