[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 actually implement this proposal as a userland lib
On Fri, Jan 24, 2014 at 12:19 PM, Facundo Domínguez <
facundo.doming...@tweag.io> wrote:
> In principle, only symbols in shared libraries can be found. However,
> the dynamic linker is able to find symbols in modules that are linked
> statically if GHC is fed with the option -optl-Wl,--export-dyna
On 24 Jan 2014, at 17:59, Carter Schonwald wrote:
> 0) I think you could actually implement this proposal as a userland library,
> at least as you've described it. Have you tried doing so?
>
I didn't pick up on that at all - how would we be able to do that?
> 1) what does this accomplish that
I don't have time to weigh in on this proposal right now, but I have several
comments...
On 24 Jan 2014, at 17:19, Facundo Domínguez wrote:
> Rationale
> ===
>
> We want the language extension to meet the following requirements:
>
> 1. It must be a practical alternative to the remoteTable
Hey Facundo,
thanks for sharing this proposal.
several questions:
0) I think you could actually implement this proposal as a userland
library, at least as you've described it. Have you tried doing so?
1) what does this accomplish that can not be accomplished by having various
nodes agree on a D
Hello,
With the support of Tweag I/O, Mathieu and I have been assembling
a design proposal for the language extension for Static values that
will take Cloud Haskell a big step forward in usability. Please, find
the proposal inlined below.
We are looking forward to discuss its feasibility a
