3 release policy

[Petr Pudlák]

+1 to be able to suppress warnings locally.

This would allow to suppress a warning that I know is OK at that place,
without suppressing the same kind of warnings elsewhere where they might be
important.

Dne st 21. 10. 2015 3:06 uživatel Evan Laforge <qdunkan at gmail.com> napsal:

> On Tue, Oct 20, 2015 at 5:48 PM, Mark Lentczner
> <mark.lentczner at gmail.com> wrote:
> > Pretty much every shop I've worked at for the last 30 years has had a
> "must
> > compile clean with no warnings" policy, no matter the language. The
> reason
>
> That's actually not true for java at google.  However, after warning
> bankruptcy was declared, a small set were made into errors and the
> rest suppressed.  So that supports the idea of categorizing warnings
> into serious and advisory, and using -Werror only for serious ones.
> Of course, choosing which ones are which is likely to be a wrangle.
>
> In my personal code I do the same, that is try to make it warning free
> but only enable warnings that I consider worthwhile.  It would also be
> really nice to have pragmas to suppress warnings locally (e.g. ErrorT
> deprecation warnings from transformers-4, which seem to be impossible
> to fix without abandoning 7.8).
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/libraries/attachments/20151021/71c85774/attachment-0001.html>