backward compatibility

Sittampalam, Ganesh ganesh.sittampalam at
Thu Jan 20 18:09:58 CET 2011

Simon Marlow wrote:

> Hopefully that explains why sometimes we make breaking changes.  If
> the 
> breaking change has a high enough impact, then it becomes worthwhile
> to 
> add backwards compatibility (via warnings / deprecation or whatever).
> Of course from the point of view of the user, the impact is always
> either high (it broke) or zero (it didn't) :-)  We have to make a
> judgement as to whether we should spend effort on backwards
> compatibility or not.  Perhaps we're getting it wrong - so feedback
> from 
> users is always valuable.

More information about the Glasgow-haskell-users mailing list