OK, will do, thanks!
Simon Marlow writes:
> Absolutely, let's get this code upstream. Just put it up on Phabricator
> and I'll be happy to review.
>
> I recall that we wanted to split up the ghci lib into modules that are
> compiled with stage0 (the client) and modules compiled with stage1 (the
Absolutely, let's get this code upstream. Just put it up on Phabricator
and I'll be happy to review.
I recall that we wanted to split up the ghci lib into modules that are
compiled with stage0 (the client) and modules compiled with stage1 (the
server). Is that a part of your plans? I think it w
No, as it currently exists it has to create a ProcessHandle, and I have
to layer some stuff on top of the iserv protocol anyway, so it wouldn't
really help much. I just use -pgmi to point to the client executable.
~Shea
Alan & Kim Zimmerman writes:
> As a matter of interest, are you making use
As a matter of interest, are you making use of `createIservProcessHook`
which allows you to set the FDs to be used when communicating with the
iserve process?
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/
