I've heard this and avoid it in many places, but I think their arguments are sound here. The maintenance effort and unexpected rebuilds needed to upkeep forward declarations is something I'm not interested in doing.
I'm not going to change my coding style because Qt Creator is broken, switching IDEs makes much more sense.
Maybe I'm wrong and I've just been made horribly lazy by writing too much C#, Python and JS, maybe this is some pretty horrible technical debt, but hopefully this will all go away once the planned C++17 modules system is introduced. It's one of my biggest annoyances with the language to date.
> Maybe I'm wrong and I've just been made horribly lazy by writing too much C#, Python and JS, ....
I know the feeling.
Nowadays I only use C++ to write libraries for Java/.NET/Android/UWP, that I have full control over.
When I see C++ code written in enterprise projects, frozen in pre-C++98, the code looks quite different, it is a continuous education process to try to convince devs to move forward, think Python 2 vs Python 3.
I also miss modules, but at least I can play with them on VC++ 2017.
I'm not going to change my coding style because Qt Creator is broken, switching IDEs makes much more sense.
Maybe I'm wrong and I've just been made horribly lazy by writing too much C#, Python and JS, maybe this is some pretty horrible technical debt, but hopefully this will all go away once the planned C++17 modules system is introduced. It's one of my biggest annoyances with the language to date.