Backward compatibility

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Backward compatibility

Simon Peyton Jones
Dear Core Libraries Committee
In addition to seeking your guidance about the comparison-primop question (a decision in the next few days would be most welcome), there are of course other breaking changes in GHC 7.8.
High on the list is Typeable (see http://ghc.haskell.org/trac/ghc/ticket/8132), which has become polykinded, which is SO much better.  Also, to guarantee the type-soundness of Typeable, we want to make it an error to use hand-rolled instances, rather than "deriving( Typeable )".  The latter is very common anyhow, and the hand-rolled ones mostly use Typeable1 which is now heavily deprecated.
There's a compatibility module Data.OldTypeable, but you'd have to import it to get the old behaviour.
It's very difficult to really provide a "bumpless transfer", which is why Michael's idea of a compatibility package might be worth exploring.
Anyway this is just a heads-up.
Simon

Microsoft Research Limited (company number 03369488) is registered in England and Wales
Registered office is at 21 Station Road, Cambridge, CB1 2FB

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20130828/70d69703/attachment.htm>