Except that warning escalates to error even when the program is doing exactly what you want.
Also that’s not what the message is saying.
Pragma warning disable did not appear to work with /WX, and compiler settings will be lost when UE4 regenerates the project, so you need to do that within the file, preferably on *.h or *.cpp level.
To turn off the warning, you first need to know WHERE the problem happens. In this case - compiler doesn’t tell you.
Unreal’s build architecture makes it very hard to pinpoint actual line where this particular warning happens. See, “ProjectName.h” includes all the headers in your project, meaning that the warning will occur in “ProjectName.generated.cpp”, and error message won’t have any mention of actual header where the problem happens.
When you use clang or gcc. Not when you use microsoft compiler. Stuff like this should be optional. ESPECIALLY for microsoft compiler.
Not sure if it is officially supported, but I was able to compile the project on update 2 after finally finding the offending initializer list in one of the hundred of headers. The compiler didn’t tell me which header had the problem. I’m not happy about compiler behavioru though. Or vc++ behavior.
I would really prefer official support for latest clang and qtcreator (instead of a wiki article).
The reason why I even run in this problem is because someone I worked with before couldn’t build one of my past projects and a programmer they asked for help couldn’t do it too.
This kind of behavior from a compiler is very bad, and any C++ beginner will with 100% certainty sink on it.