From: "Luca de Alfaro" <luca@dealfaro.org>
To: "Loup Vaillant" <loup.vaillant@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Vec: a functional implementation of extensible arrays
Date: Thu, 19 Jul 2007 09:59:14 -0700 [thread overview]
Message-ID: <28fa90930707190959g66cb2e6wc7a446af2a6dfb72@mail.gmail.com> (raw)
In-Reply-To: <6f9f8f4a0707190045g609abca4kfa3bb39d93604081@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3105 bytes --]
On 7/19/07, Loup Vaillant <loup.vaillant@gmail.com> wrote:
>
> 2007/7/18, Luca de Alfaro <luca@dealfaro.org>:
> > Dear All,
> >
> > I would like to share with you an Ocaml implementation of extensible
> arrays.
> > The implementation is functional, based on balanced trees (and on the
> code
> > for Set and Map); I called the module Vec (for vector - I like
> > short names). You can find it at
> > http://www.dealfaro.com/home/vec.html
> > Module Vec provides, in log-time:
> >
> > Access and modification to arbitrary elements ( Vec.put n el v puts
> element
> > el in position n of vector v, for instance).
> > Concatenation
> > Insertion and removal of elements from arbitrary positions
> (auto-enlarging
> > and auto-shrinking the vector).
> > as well as:
> >
> > All kind of iterators and some visitor functions.
> > Efficient translation to/from lists and arrays.
> > An advantage of Vec over List, for very large data structures, is that
> > iterating over a Vec of size n requires always stack depth bounded by
> log n:
> > with lists, non-tail-recursive functions can cause stack overflows.
> >
> > I have been using this data structure for some months, and it has been
> very
> > handy in a large number of occasions. I hope it can be as useful to
> you.
> >
> > I would appreciate all advice and feedback. Also, is there a repository
> > where I should upload it? Do you think it is worth it?
> >
> > All the best,
> >
> > Luca
>
> Very interesting. I always felt uneasy about the presence of
> imperative arrays without a functional counterpart. I can't wait to
> try it.
>
> Looking at your array type definition, I assume that the timings you
> specified are worst-case? Is it possible to achieve better (but
> amortized) bounds? Do you think it would be worth the trouble?
>
> I didn't see in your specs the complexity of your iterators. Does
> these work in linear time, like those of the List and Array module?
>
> Regards,
> Loup
For get/set, the worst case and the average case are both logarithmic: it's
a balanced tree (if you are lucky, you can find your answer at the root!
;-). I am open to new ideas. In part, I wanted a simple data structure
(easier to extend, among other things). Also, I use Set, Map, etc, quite
often, and those are also balanced trees: I thought that if I can live with
those, I can probably live with Vec as well.
For an iterator, the worst case is as follows, where n is the size of the
Vec:
- if you iterate on the whole Vec, then O(n)
- if you iterate over m elements (you can iterate on a subrange), then
O(m + log n).
That's why I have iterators: you can also iterate via a for loop, using get
to access the elements, but then the time becomes O(n log n) for the first
case, and O(m log n) for the second case.
Luca
_______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 4125 bytes --]
next prev parent reply other threads:[~2007-07-20 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 17:32 Luca de Alfaro
2007-07-19 7:45 ` [Caml-list] " Loup Vaillant
2007-07-19 8:17 ` Hugo Ferreira
2007-07-19 16:51 ` Luca de Alfaro
2007-07-19 17:13 ` Luca de Alfaro
2007-07-19 16:59 ` Luca de Alfaro [this message]
2007-07-20 7:35 ` Loup Vaillant
2007-07-20 8:14 ` Jon Harrop
2007-07-20 15:42 ` Luca de Alfaro
2007-07-20 16:45 ` Brian Hurt
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=28fa90930707190959g66cb2e6wc7a446af2a6dfb72@mail.gmail.com \
--to=luca@dealfaro.org \
--cc=caml-list@yquem.inria.fr \
--cc=loup.vaillant@gmail.com \
/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