On Fri, Jan 9, 2015 at 11:18 AM, Jan Stolarek <jan.stola...@p.lodz.pl> wrote:
> > I agree. You'll get rid of the redundancy in the library by removing it > but > > you're users will have to live with (...) > That's why I want to deprecate them first and give users one release cycle > to switch to new > functions. I assumed that's enough but we could make this two or three > release cycles. The reall > question is how to remember that we should remove this at some point? > If we want to avoid the CPP we need warning to be in major version X if that's when the old function is deprecated and the new one is added and the actual removal in X+2. At that point I'd just consider keeping the function and avoid the hassle. :)
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
