From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Ropes and rope-like functional extensible vectors with O(1) prepend/append.
Date: Mon, 30 Jul 2007 01:46:20 +0100 [thread overview]
Message-ID: <200707300146.20940.jon@ffconsultancy.com> (raw)
In-Reply-To: <20070728233305.GB28879@tux-chan>
On Sunday 29 July 2007 00:33:05 Mauricio Fernandez wrote:
> It is still young and experimental, but it's maybe worth a look. Any
> feedback is very welcome.
Looks awesome!
It seems to use mutation internally. Is it not thread safe?
I have some suggestions:
I'd like metadata in every node, so I can provide a constructor that combines
the metadata of child nodes and a cull function to accelerate searches.
The usual HOFs, like map.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
OCaml for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists/?e
next prev parent reply other threads:[~2007-07-30 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 23:33 Mauricio Fernandez
2007-07-30 0:46 ` Jon Harrop [this message]
2007-07-30 11:51 ` [Caml-list] " Mauricio Fernandez
2007-07-30 13:47 ` Jon Harrop
2007-07-31 23:55 ` Mauricio Fernandez
2007-08-04 10:36 ` Jon Harrop
2007-08-09 22:07 ` Nathaniel Gray
2007-08-21 21:39 ` Luca de Alfaro
2007-08-22 2:54 ` skaller
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=200707300146.20940.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@inria.fr \
/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).