Sorry, here's my explanation.
In summary, I was trying to go for the cleanest, tidiest, simplest AST
possible for interpretation. My long-term goal is to have a slow but
working interpreter of GHC Haskell written in Haskell that is capable
of hot-swapping without segfaulting, by gracefully handlin
Matthew Pickering writes:
> I am in favor of option b) as it fits in better with the "gitlab way
> of things". If we are to use gitlab then we should use it as it's most
> intended rather than trying to retrofit trac practices which have
> accrued over many years.
>
> Adding commits as comments i
GHC newcomer here -- attempting to work on my first patch.
I decided to try Hadrian, but ran into a problem.
I think I obtained the source using
> git clone --recursive https://gitlab.haskell.org/ghc/ghc
Then:
> ./boot && ./configure
> hadrian/build.sh -j --flavour=devel2
This ran for maybe 15 m
