From: cousinea@dmi.ens.fr
To: Xavier Leroy <xavier@Theory.Stanford.EDU>
Cc: caml-list@margaux
Subject: Re: new library modules
Date: Tue, 4 May 93 11:14:37 +0200 [thread overview]
Message-ID: <9305040914.AA08481@arnica.ens.fr> (raw)
The sets that you propose are not only totally ordered sets
but rather totally pre-ordered and I think that it is indeed important
for many applications. It is very often the case that you have
to deal with a set of complex objects a part which is used for
the pre-order relation.
In that case, you will probably suggest to use a "map" but "maps"
do not allow for multiple bindings.
I have myself written a library for balanced trees and used it for
several applications. I have found that, when dealing with equivalent
elements, it is sometimes useful
- to allow equivalent elements to occur simultaneously in the tree.
- to allow the user to precise, when using function "add" , the treatment
he/she wants to be performed on equivalent elements (keeping both,
keeping the old one, replacing the old one by the new one)
I am conscious that this goes beyond "set" operations but you get
these possibilities almost for free when you have balanced trees
based on a pre-order relation.
Why not let us have access directly to your balanced trees package?
Also:
Rather than using type "int" for comparison, it would be clearer
to use an explicit type comparison= Smaller | Equiv | Greater.
next reply other threads:[~1993-05-04 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-04 9:14 cousinea [this message]
1993-05-04 9:38 ` Vale'rie Me'nissier-Morain
1993-05-05 2:25 ` Xavier Leroy
-- strict thread matches above, loose matches on Subject: below --
1993-05-07 10:29 cousinea
1993-05-07 10:23 cousinea
1993-05-05 9:53 Damien Doligez
1993-05-03 18:45 Xavier Leroy
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=9305040914.AA08481@arnica.ens.fr \
--to=cousinea@dmi.ens.fr \
--cc=caml-list@margaux \
--cc=xavier@Theory.Stanford.EDU \
/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