From: Radu Grigore <radugrigore@gmail.com>
To: fa.caml@googlegroups.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Poset variant of union-find datastructure
Date: Fri, 29 Jul 2011 08:50:21 -0700 (PDT) [thread overview]
Message-ID: <5491ca2c-2f03-4c6f-a915-edc7ef6f79a0@glegroupsg2000goo.googlegroups.com> (raw)
In-Reply-To: <fa.4YXCBZTjiruOkOWERgIhmlS84TY@ifi.uio.no>
On Wednesday, July 27, 2011 9:22:16 PM UTC+1, Guillaume Yziquel wrote:
> I'm wondering if people on this list may have any insight as to how
> implement a "poset-find" datastructure much like a union-find
> datastructure.
What you want is known as "dynamic transitive closure" or, more precisely, "incremental transitive closure." See, for example,
http://scholar.google.co.uk/scholar?cluster=2214623839872244490
as a starting point.
next parent reply other threads:[~2011-07-29 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.4YXCBZTjiruOkOWERgIhmlS84TY@ifi.uio.no>
2011-07-29 15:50 ` Radu Grigore [this message]
2011-07-27 20:20 Guillaume Yziquel
2011-07-28 8:53 ` Christophe Raffalli
2011-07-28 17:03 ` Guillaume Yziquel
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=5491ca2c-2f03-4c6f-a915-edc7ef6f79a0@glegroupsg2000goo.googlegroups.com \
--to=radugrigore@gmail.com \
--cc=caml-list@inria.fr \
--cc=fa.caml@googlegroups.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