From: Radu Grigore <radugrigore@gmail.com>
To: Jon Harrop <jon@jdh30.plus.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Complexity of Set.union
Date: Fri, 25 Feb 2005 23:52:57 +0200 [thread overview]
Message-ID: <7f8e92aa05022513527a1b794@mail.gmail.com> (raw)
In-Reply-To: <7f8e92aa0502251350202ec368@mail.gmail.com>
On Fri, 25 Feb 2005 23:50:25 +0200, Radu Grigore <radugrigore@gmail.com> wrote:
> > > That
> > > could indeed run in constant time (just join the two sets with a
> > > "Node" constructor), but I doubt the current implementation achieves
> > > this because of the repeated splitting.
>
> What splitting? I see none in this case.
30s later and I see it :)
--
regards,
radu
http://rgrig.blogspot.com/
next prev parent reply other threads:[~2005-02-25 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 9:20 Set union Jon Harrop
2005-02-25 10:56 ` [Caml-list] " Radu Grigore
2005-02-25 17:30 ` Jon Harrop
2005-02-25 17:48 ` Xavier Leroy
2005-02-25 19:47 ` [Caml-list] Complexity of Set.union Jon Harrop
2005-02-25 21:50 ` Radu Grigore
2005-02-25 21:52 ` Radu Grigore [this message]
2005-02-25 22:31 ` Radu Grigore
2005-02-25 22:36 ` Jon Harrop
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=7f8e92aa05022513527a1b794@mail.gmail.com \
--to=radugrigore@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@jdh30.plus.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;
as well as URLs for NNTP newsgroup(s).