Making GHCi awesomer?

[Christopher Done]

On 18 October 2014 19:05, Mateusz Kowalczyk <fuuzetsu at fuuzetsu.co.uk> wrote:

> Sounds interesting. My only request/comment is that I hope whatever
> conclusion you come to, the library part of it will be usable just as
> much (or even more) as the executable: if we can talk to the library
> natively then that's much easier than talking to some remote socket and
> parsing out data.
>

I'm not sure what GHC HQ would think of GHCi exposing an API, but certainly
I'm for it. Yi would have no reason to talk via JSON API if it could just
call the functions in a type-safe way directly, or at least have an API
that does the talking to the remote socket so that you don't have to.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20141018/e93bc4d4/attachment.html>