Template Haskell and haskell-src-exts

[Simon Peyton-Jones]

Hmm, that would be rather unfortunate. But if we go with my suggested split of functionality betweeen template-haskell and haskell-src-exts, it should be enough to lock down the version of template-haskell, right? As long as the template-haskell version depends on the expected version of haskell-src-exts, installing newer versions of haskell-src-exts should still be possible. Or am I missing something?

I believe that's right.
Simon


From: cvs-ghc-bounces at haskell.org [mailto:cvs-ghc-bounces at haskell.org] On Behalf Of Niklas Broberg
Sent: 18 September 2012 19:01
To: cvs-ghc at haskell.org
Subject: Re: Template Haskell and haskell-src-exts

On Tue, Sep 18, 2012 at 7:11 PM, Ian Lynagh <ian at well-typed.com<mailto:ian at well-typed.com>> wrote:
It's true that in principle you could use a different version of
template-haskell (or haskell-src-exts, in the future) provided you were
only using its datastructures for other things, not for Template
Haskell. However, I think it would result in a lot less confusion if we
simply have cabal disallow installing a different version of
template-haskell/haskell-src-exts than comes with the compiler.

Hmm, that would be rather unfortunate. But if we go with my suggested split of functionality betweeen template-haskell and haskell-src-exts, it should be enough to lock down the version of template-haskell, right? As long as the template-haskell version depends on the expected version of haskell-src-exts, installing newer versions of haskell-src-exts should still be possible. Or am I missing something?

Cheers,

/Niklas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cvs-ghc/attachments/20120919/2c1765f3/attachment.htm>