caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mark Shinwell <mshinwell@janestreet.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: "Peter Zotov" <whitequark@whitequark.org>,
	"Daniel Bünzli" <daniel.buenzli@erratique.ch>,
	"Benjamin Canou" <benjamin.canou@gmail.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] proposal for finding, loading and composing ppx preprocessors
Date: Fri, 11 Jul 2014 16:35:52 +0100	[thread overview]
Message-ID: <CAM3Ki75FrjinJAz8zS+j5WjCzc4Nzqmm-L7o9Etg3YzHz9cagw@mail.gmail.com> (raw)
In-Reply-To: <D89DCD4F-ECFA-454E-884B-178B3BD7A6A4@recoil.org>

On 11 July 2014 16:27, Anil Madhavapeddy <anil@recoil.org> wrote:
> On 11 Jul 2014, at 15:36, Peter Zotov <whitequark@whitequark.org> wrote:
> Personally, I'd love to see the use of Sys replaced with the Irmin Git
> library database (http://github.com/mirage/irmin).  This would allow a model
> where the ML sources are imported into a Git DAG, passed through to the
> compiler-libs as an in-memory structure, and the intermediate results
> recorded in the DAG, still all in-memory.
>
> When the build has completed, the Irmin DAG could be dumped to disk in
> the Git file format, permitting the entire build process to be inspected
> if necessary (or GCed if not).  All the Git bits are currently supported
> by Irmin, so this project just requires an intrepid hacker to connect
> compiler-libs, Irmin, and some coordination glue.

For those who don't know, we have discussed the idea of using Jenga, a
new dependency engine and build system under development at Jane
Street to do the "coordination" part.  This isn't (yet) being actively
developed, but I'd be pleased to hear from anyone who might be
interested in hacking on this.

Mark

  reply	other threads:[~2014-07-11 15:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 13:31 Benjamin Canou
2014-07-11 14:21 ` Daniel Bünzli
2014-07-11 14:36   ` Peter Zotov
2014-07-11 14:49     ` Daniel Bünzli
2014-07-11 14:55       ` Peter Zotov
2014-07-11 14:52     ` Mark Shinwell
2014-07-11 15:27     ` Anil Madhavapeddy
2014-07-11 15:35       ` Mark Shinwell [this message]
2014-07-11 14:55   ` Benjamin Canou
2014-07-11 15:23     ` Daniel Bünzli
2014-07-11 16:00       ` Benjamin Canou
2014-07-11 16:13 ` Alain Frisch
2014-07-15 13:59   ` Benjamin Canou
2014-07-15 15:56     ` Alain Frisch

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=CAM3Ki75FrjinJAz8zS+j5WjCzc4Nzqmm-L7o9Etg3YzHz9cagw@mail.gmail.com \
    --to=mshinwell@janestreet.com \
    --cc=anil@recoil.org \
    --cc=benjamin.canou@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --cc=whitequark@whitequark.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;
as well as URLs for NNTP newsgroup(s).