Mathieu Boespflug wrote:
> [Sorry for the multiple reposts - couldn't quite figure out which
> email address doesn't get refused by the list..]
>
>
> Hi Carter,
>
> thank you for the good points you raise. I'll try and address each of
> them as best I can below.
>
> > 0) I think you could actu
Escuse me, the module export list was meant to be
> module Communicate(runExpect, runSend) where
Facundo
On Tue, Jan 28, 2014 at 5:13 PM, Facundo Domínguez
wrote:
> Hello Carter,
> Thanks for the links. IIUC the ObjLink module contains an interface
> to the RTS linker. The points raised by Ma
Hello Carter,
Thanks for the links. IIUC the ObjLink module contains an interface
to the RTS linker. The points raised by Mathieu in his last email as
(1a), (1b) and (2) still hold.
Here's a use case for (2):
module Communicate(run)
import Control.Distributed.Process
f :: Int -> Int
f = id
r
Theres actually a missing piece of information in this thread: what are the
example computations that are being sent?
My understanding is that erlang has not way to send file handles, shared
variables, Tvars, Mvars, memory mapped binary files, GPU code / memory
pointers , and other fun unportable t
Hi Mathieu,
On 28 Jan 2014, at 12:53, Mathieu Boespflug wrote:
> We would prefer to do it that way, to be honest. As explained in my
> previous email, we identified two problems with this approach:
>
> 1) User friendliness. It's important for us that Cloud Haskell be
> pretty much as user friendl
On Tue, Jan 28, 2014 at 7:53 AM, Mathieu Boespflug wrote:
> On Sat, Jan 25, 2014 at 7:12 PM, Carter Schonwald
> wrote:
> > 1) you should (once 7.8 is out) evaluate how far you can push your ideas
> wrt
> > dynamic loading as a user land library.
> > If you can't make it work as a library and ca
Hi Carter, Tim,
On Sat, Jan 25, 2014 at 7:12 PM, Carter Schonwald
wrote:
> anyways
>
> 1) you should (once 7.8 is out) evaluate how far you can push your ideas wrt
> dynamic loading as a user land library.
> If you can't make it work as a library and can demonstrate why (or how even
> though it
To address the concerns about static linking and portability, there is
also the alternative of of using the RTS linker in those platforms
that need it.
In many aspects, neither linker makes a big difference to us. We are
going with the system's dynamic linker mainly because GHC team has
expressed
