but why?
-
-
-
Compilers add new warnings all the time. If somebody tries to build your code with a newer compiler than the developer used (which is likely, if they're building anything other than very recently written code), they may hit a new warning and then get compilation failures.
- 1 more reply
New conversation -
-
-
As long as CI builds have `-Wall -Werror`, I don’t much care what people do locally on their machines. But *something* needs that level of rigor or else you release this: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
likewise with rust's #![deny(warnings)]
-
I don't think errors from warnings in dependencies actually error the build.
End of conversation
New conversation -
-
-
-Weverything -Werror -Wno-...someWarnings has served us very well so far, but we do not make public builds. If you can enforce this for CI builds and be a lot more per missing on public builds great... but then you need to have a well diverse and updated CI agents setup.
-
Some of those warnings only your customers get may be important.
End of conversation
New conversation -
-
-
This. So much this
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Watch the world burn -Wall -Weverything -Wpedantic -Werror
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
using