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: [email protected] [mailto:[email protected]] On Behalf Of Niklas Broberg Sent: 18 September 2012 19:01 To: [email protected] Subject: Re: Template Haskell and haskell-src-exts On Tue, Sep 18, 2012 at 7:11 PM, Ian Lynagh <[email protected]<mailto:[email protected]>> 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
_______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
