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 https://ghc.haskell.org/trac/ghc/wiki/ImplementingTreesTh
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 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 sta
Hi David,
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.
- Why not making Core growable as well?
We just have not co
