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
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 te
On Tue, Sep 18, 2012 at 04:28:34PM +, Simon Peyton-Jones wrote:
> | 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/h
Original Message-
| From: Ian Lynagh [mailto:i...@well-typed.com]
| Sent: 18 September 2012 15:44
| To: Thomas Schilling
| Cc: Simon Peyton-Jones; Niklas Broberg; cvs-ghc@haskell.org
| Subject: Re: Template Haskell and haskell-src-exts
|
| On Mon, Sep 17, 2012 at 10:47:10PM +0100, Th
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
In principle this sounds good. I just thought I'd mention
http://hackage.haskell.org/trac/ghc/ticket/3355
which is related, though not directly.
Cheers,
Simon
On 15/09/2012 09:32, Simon Peyton-Jones wrote:
Niklas
Yesterday we discussed the possibility of merging your haskell-src-e
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?
On 15 September 2012 09:32, Simon Peyton-Jones wrote:
> Nikl
I have an alternative proposal:
* haskell-src-exts (HSE) remains as it is now (modulo any changes that
simply must be made to allow TH functionality, e.g. the Name type)
* template-haskell is changed to depend on HSE for all the basic AST
functionality, but defines the purely meta-level
Orthogonal; but would make sense as part of the same Big Bang
Simon
From: Richard Eisenberg [mailto:e...@cis.upenn.edu]
Sent: 17 September 2012 15:25
To: Simon Peyton-Jones
Cc: Niklas Broberg; cvs-ghc@haskell.org
Subject: Re: Template Haskell and haskell-src-exts
How does this relate to
http
How does this relate to
http://hackage.haskell.org/trac/ghc/blog/Template%20Haskell%20Proposal ?
I seem to recall seeing an email/post/something recently indicating that the
plan on the wiki page was currently being implemented.
Thanks,
Richard
On Sep 15, 2012, at 4:32 AM, Simon Peyton-Jones w
Niklas
Yesterday we discussed the possibility of merging your haskell-src-exts and the
template-haskell library, as part of your vision for a Haskell Suite.
Motivation. It's stupid, stupid to have both the large Language.Haskell.TH
data types for Haskell and the large Language.Haskell.Exts dat
11 matches
Mail list logo
