RE: Template Haskell and haskell-src-exts

| If I've understood correctly, then haskell-src-exts would be more than
| just a boot package: It would be intimately tied to GHC. Any change in
| its interface would need to be reflected in the compiler (e.g.
| compiler/hsSyn/Convert.lhs, compiler/deSugar/DsMeta.hs).

Yes, that would be right.  In a sense containers is like that too though; if Data.Map is changed, so much GHC's source code change.  Does that make it "more than a boot package"?  But the coupling is particularly intimate for TH; GHC must know about every data constructor in the syntax tree.

Simon

| -----Original Message-----
| From: Ian Lynagh [mailto:[email protected]]
| Sent: 18 September 2012 15:44
| To: Thomas Schilling
| Cc: Simon Peyton-Jones; Niklas Broberg; [email protected]
| Subject: Re: Template Haskell and haskell-src-exts
| 
| On Mon, Sep 17, 2012 at 10:47:10PM +0100, Thomas Schilling wrote:
| > Wouldn't that make haskell-src-exts a boot package?  I think that
| > would mean that users could upgrade haskell-src-exts independently,
| > but won't be able to use the upgraded version and TH in the same
| > program.  Or am I missing something?
| 
| If I've understood correctly, then haskell-src-exts would be more than
| just a boot package: It would be intimately tied to GHC. Any change in
| its interface would need to be reflected in the compiler (e.g.
| compiler/hsSyn/Convert.lhs, compiler/deSugar/DsMeta.hs).
| 
| I'd suggest that it be added to the list of packages that cabal doesn't
| upgrade by default (http://hackage.haskell.org/trac/ghc/ticket/7200).
| 
| 
| Thanks
| Ian
|