Closed SpaceIm closed 1 year ago
Has conflicts now but these aggressive flags are good either way. Also for production. After all it needs to be 100% watertight in a realtime env.
When a new version of a compiler is released, it comes with new warnings, but it doesn't mean that generated binaries are worse with this new compiler version just because new warnings are displayed. When you force warnings as errors unconditionally, you make things harder for package managers which have to support old libraries versions with new compiler versions.
allows to disable these flags which may break build with more recent compilers due to new warnings