Sorry Facundo I didn't realise this reply had remaining questions in it.
On Mon, May 30, 2022 at 3:35 AM Domínguez, Facundo
wrote:
>
> Thanks Matthew for your pointers.
>
> Since originally posting, I managed to simplify the problem by terminating
> the compilation server at the end of a build,
Thanks Matthew for your pointers.
Since originally posting, I managed to simplify the problem by terminating
the compilation server at the end of a build, which allows to introduce the
assumption that the code doesn't change during the lifetime of the server.
Now, I'm observing that sometimes dif
Hi Facundo
Some pointers...
1. Only put things in the EPS if they are not going to change
throughout the whole compilation
2. Treat everything which can change as a home package
2a. I suppose you have performed your own dependency analysis, so
build your own `ModGraph` and start looking from `loa
Dear ghc devs,
I'm using the ghc API to write a compilation server (a.k.a. persistent
worker). The idea is to serve requests to compile individual modules. In
this fashion, we can compile modules with different compilation flags and
yet pay only once for the startup overheads of the compiler.
One
