Changes to primops break libraries (was Re: 7.8 Feature window)

Simon Marlow marlowsd at
Mon Aug 26 12:15:16 CEST 2013

On 26/08/13 10:38, Jan Stolarek wrote:
>> So since we have to break the API anyway, why not break it in the way
>> that we want?
> Oh, but the thing is we don't! We have a plan to rename GHC.Prim to GHC.Prim.BuiltIn, rename
> GHC.PrimWrappers (in ghc-prim) to GHC.Prim and make it re-export GHC.Prim.BuiltIn [1]. This way
> change will be completely backwards compatible. I was working on that on Friday. Patches are
> essentially finished, but I still have to solve haddock panic that I somehow introduced [2].

I'm sorry, but I just don't like this solution.  We could do this every 
time we change an API, but imagine what a mess we'd be in by now!  It's 
just not the right way to manage API changes.


More information about the ghc-devs mailing list