3 release policy

[Dmitry Olshansky]

Personally as user of libraries I have no problem with warnings. Because
- I can't improve it
- I got it only once when install library

I just care about warnings in my projects and that is not so hard.

So I want to say that it is not a big deal. Perhaps warning's levels are
good but simplicity is more important for me.

Dmitry

2015-10-20 22:55 GMT+03:00 Jeremy <voldermort at hotmail.com>:

> A "3 release policy" has been recently mentioned several times, whereby it
> should always be possible to write code that compiles with the last three
> releases of GHC, without generating any -Wall warnings.
>
> The no warning requirement seems excessively harsh. Will early warnings of
> impending breakage really cause so much trouble that accepted proposals
> have
> to be dragged out over several years to avoid them? If so, would a flag to
> suppress the warnings suffice?
>
> I should note that GHC has traditionally had no qualms about introducing
> new
> warnings, on by default.
>
>
>
> --
> View this message in context:
> http://haskell.1045720.n5.nabble.com/3-release-policy-tp5820363.html
> Sent from the Haskell - Libraries mailing list archive at Nabble.com.
> _______________________________________________
> 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/20151022/a95226aa/attachment.html>