rg
| Subject: Re: Trees that Grow in the hsSyn AST
|
| On Friday, May 26, 2017 9:03:15 AM EDT Simon Peyton Jones wrote:
| > 1. Which is better to start with: HsSyn or Core? Intuition suggests
| this sort of thing could be very helpful for making zapping more reliable
| and ensuring its effici
On Friday, May 26, 2017 9:03:15 AM EDT Simon Peyton Jones wrote:
> 1. Which is better to start with: HsSyn or Core? Intuition suggests this sort
> of thing could be very helpful for making zapping more reliable and ensuring
> its efficiency, but there may be better reasons to start with HsSyn.
>
Peyton Jones <simo...@microsoft.com>; Alan & Kim Zimmerman
<alan.z...@gmail.com>; ghc-devs@haskell.org
Subject: RE: Trees that Grow in the hsSyn AST
I haven't looked in detail yet, but there seem to be good ideas. I have two
questions:
1. Which is better to start with: HsSyn or
ation
> (unbound, bound, abt, etc)?
>
>
> David Feuer
> Well-Typed, LLP
>
> Original message
> From: Simon Peyton Jones via ghc-devs <ghc-devs@haskell.org>
> Date: 5/25/17 6:48 PM (GMT-05:00)
> To: Alan & Kim Zimmerman <alan.
ghc-devs@haskell.org> Date: 5/25/17 6:48 PM (GMT-05:00) To: Alan & Kim
Zimmerman <alan.z...@gmail.com>, ghc-devs@haskell.org Subject: RE: Trees that
Grow in the hsSyn AST
Folks
Do take a look at this:
· We propose to re-engineer HsSyn itself. This will tou
Folks
Do take a look at this:
·We propose to re-engineer HsSyn itself. This will touch a lot of code.
·But it’s very neat, and will bring big long-term advantages
·And we can do it a bit at a time
The wiki page
