On Thu, May 25, 2017 at 08:31:24AM -0400, Ehsan Akhgari wrote:
What was the motivation behind this change? Was there a complaint from a significant number of developers about it being difficult fixing compiler warnings grepping for things like "warning:" or using ./mach warnings-list? Was the feedback from developers who have the use case of writing code and fix compiler errors in such code taken into account?
For what it's worth, I've often wished for something like this when watching huge numbers of warnings flow by in NSS and media code, if only to motivate people to fix them. But the fact that we compile with -Werror and generally only get warnings in third-party code (ignoring NSS and NSPR) means that they're effectively pretty useless, and we'd be better off just disabling warnings in that code.
What I really want at the end of a compile is a list of warnings and errors that matter, rather than a lot of useless warning spew that makes it harder to find the ones that do among the ones that don't.
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
