Hi, We ran into this problem recently. In my opinion this is a somewhat serious problem with Qt that should be fixed.
We noticed this after fixing a bug in our code. A function was incorrectly taking an int argument instead of a double argument, and we were passing a double in. But the usual warning was not reported The usual warning would be something like:
warning C4244: 'initializing' : conversion from 'double' to 'int', possible loss of dataAfter a little experimentation I determined that the Qt headers are effectively suppressing warnings for all code after they are included, due to the use of #pragma warning in qglobal.h as noted in this bug report.
I don't think it's a good idea for Qt to disable warnings like this such that it effects user code. If Qt wasn't doing this we would have probably found our bug much earlier.
One possible solution is to use #pragma warning push at the start of qt headers, then #pragma warning pop at the end.
In my opinion, 'polluting' the compiler warning state in the way qt does is bad form, and is similar to 'using namespace std' in a header file, which we all know is a bad idea.
Although there is a QT_NO_WARNINGS option, I think it's a good idea to try fixing with the pragma pop idea above. Having an option is better than nothing, but Qt should not have dodgy behaviour by default.
EDIT: Discussion on Reddit