From: Alain Frisch <Alain.Frisch@inria.fr>
To: "Bauer, Christoph" <Christoph.Bauer@lms-gmbh.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: AW: [Caml-list] OCaml troll on Slashdot
Date: Fri, 18 Mar 2005 09:35:27 +0100 [thread overview]
Message-ID: <423A92CF.1060103@inria.fr> (raw)
In-Reply-To: <D981925B4F2CD611870300E0184CEE9B0157F581@kaiserslautern1.lmsintl.com>
Bauer, Christoph wrote:
> There is an implementation of VLists for OCaml. VLists are - like
> single linked lists - persistent, but have better performance,
> require less memory and are GC friendlier.
This depends on the kind of operation you need: the VList.tl operation
is more complex and always incurs memory allocation (this can be avoided
in theory, but it seem difficult to do it in OCaml). In particular, if
you implement the map function using only VList.tl and VList.hd, the
result will probably be much slower than with lists (of course, there is
a more efficient VList.map, but it cannot be written using only the
VList API).
-- Alain
prev parent reply other threads:[~2005-03-18 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 8:16 Bauer, Christoph
2005-03-18 8:35 ` Alain Frisch [this message]
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=423A92CF.1060103@inria.fr \
--to=alain.frisch@inria.fr \
--cc=Christoph.Bauer@lms-gmbh.de \
--cc=caml-list@yquem.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