I've answered all these questions (I hope) in the form of new Notes and
signposts, please feel free to comment on this diff:
https://phabricator.haskell.org/D2358. I'm happy to add more if needs be.
On 22 June 2016 at 16:39, Richard Eisenberg wrote:
>
> On Jun 22, 2016, at 10:38 AM, Simon Marlo
On Jun 22, 2016, at 10:38 AM, Simon Marlow wrote:
> Thanks for the feedback Richard. It's helpful to know which parts of the
> implementation you found non-obvious. I will write some more Notes, but
> first:
I think what would help most is a place that describes the little state machine
th
M, Simon Peyton Jones via ghc-devs <
> ghc-devs@haskell.org> wrote:
>
> It’s a great start, thanks
>
> Simon
>
> *From:* Simon Marlow [mailto:marlo...@gmail.com]
> *Sent:* 22 June 2016 12:32
> *To:* Simon Peyton Jones
> *Cc:* ghc-devs@haskell.org
> *Subject:
Yes - I wasn't planning on dropping support for the in-process interpreter,
for that reason.
I haven't thought about plugins very much, but aren't they always compiled
code? We don't need an in-process interpreter for those, but we do need
in-process linking. Maybe that doesn't simplify things m
Hello Simon,
I have no exception to having it be default and dropping the special
case support for building profiled/dynamic so that TH works. But
I don't think support for loading code in-process for GHC should be dropped,
c.f. Manuel's email
https://mail.haskell.org/pipermail/ghc-devs/2015-Nove
> On Jun 22, 2016, at 8:27 AM, Simon Peyton Jones via ghc-devs <
> ghc-devs@haskell.org> wrote:
>
> It’s a great start, thanks
>
> Simon
>
> *From:* Simon Marlow [mailto:marlo...@gmail.com]
> *Sent:* 22 June 2016 12:32
> *To:* Simon Peyton Jones
> *Cc:* ghc-dev
> It’s a great start, thanks
>
> Simon
>
> From: Simon Marlow [mailto:marlo...@gmail.com]
> Sent: 22 June 2016 12:32
> To: Simon Peyton Jones
> Cc: ghc-devs@haskell.org
> Subject: Re: Require -fexternal-interpreter support for future TH changes?
>
> How's
It’s a great start, thanks
Simon
From: Simon Marlow [mailto:marlo...@gmail.com]
Sent: 22 June 2016 12:32
To: Simon Peyton Jones
Cc: ghc-devs@haskell.org
Subject: Re: Require -fexternal-interpreter support for future TH changes?
How's this?
https://ghc.haskell.org/trac/ghc/wiki/Comme
mplementing a message type…” but I don’t know what that
>> library is called or where it lives.
>>
>
> Yes, we should really have a page in the commentary with an overview of
> the pieces and the main implementation strategy. I'll write one.
>
> Cheers
> Simon
Yes, we should really have a page in the commentary with an overview of the
pieces and the main implementation strategy. I'll write one.
Cheers
Simon
>
>
> Thanks
>
>
>
> Simon
>
>
>
> *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of *Simo
To: ghc-devs@haskell.org
Subject: Require -fexternal-interpreter support for future TH changes?
Background
A few months ago I added -fexternal-interpreter to GHC:
* docs:
http://downloads.haskell.org/~ghc/latest/docs/html/users_guide/ghci.html#ghc-flag--fexternal-interpreter<https://n
*Background*
A few months ago I added -fexternal-interpreter to GHC:
- docs:
http://downloads.haskell.org/~ghc/latest/docs/html/users_guide/ghci.html#ghc-flag--fexternal-interpreter
- wiki, rationale: https://ghc.haskell.org/trac/ghc/wiki/RemoteGHCi
When -fexternal-interpreter is used,
12 matches
Mail list logo
