From: Arthur Breitman <arthur.breitman@gmail.com>
To: Thomas Gazagnaire <thomas@gazagnaire.org>
Cc: caml-list <caml-list@inria.fr>, Goswin von Brederlow <goswin-v-b@web.de>
Subject: Re: [Caml-list] Keeping A big data optimization problem functional
Date: Wed, 16 Apr 2014 05:02:02 -0600 [thread overview]
Message-ID: <CAAYUt0P=N+qr-k+RRZoCwzns5Fo8cy6TxhzCMkUQO6xgkOEWSQ@mail.gmail.com> (raw)
In-Reply-To: <08C4CEED-FAFF-49CE-9890-7A45C802CF02@gazagnaire.org>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Apr 15, 2014 9:50 AM, "Thomas Gazagnaire" <thomas@gazagnaire.org> wrote:
>
> > type node = {value: string; children: node list option}
> > module type Context = begin
> > type t
> > val apply: t -> node -> t
> > val get: t -> string -> string option
> > val set: t -> string -> string -> t
> > val fitness -> int
> > val empty -> t
> > end
>
> What's the link between nodes and elements of your store ?
The only link between the two is the existence of the parametric "apply"
function.
For all intent and purposes, you can think of the nodes as functions
operating on elements of type "register".*
--
Arthur
* in reality it's a little more complicated as the apply function can
return a register with a different apply function, but for our purpose it's
irrelevant
>
> --
> Thomas
[-- Attachment #2: Type: text/html, Size: 1192 bytes --]
next prev parent reply other threads:[~2014-04-16 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 5:25 Arthur Breitman
2014-04-14 5:43 ` Francois Berenger
2014-04-14 6:07 ` Arthur Breitman
2014-04-14 8:12 ` Goswin von Brederlow
2014-04-14 19:32 ` Arthur Breitman
2014-04-15 9:05 ` Goswin von Brederlow
2014-04-15 13:16 ` Arthur Breitman
2014-04-15 13:50 ` Thomas Gazagnaire
2014-04-16 11:02 ` Arthur Breitman [this message]
2014-04-14 20:38 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAYUt0P=N+qr-k+RRZoCwzns5Fo8cy6TxhzCMkUQO6xgkOEWSQ@mail.gmail.com' \
--to=arthur.breitman@gmail.com \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.de \
--cc=thomas@gazagnaire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox