From: Brian Hurt <bhurt@spnz.org>
To: Matthieu Sozeau <mattam@altern.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Map + Set
Date: Mon, 26 Jul 2004 10:25:28 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0407261016000.6739-100000@localhost.localdomain> (raw)
In-Reply-To: <20040726104051.GA9736@mattam.ath.cx>
On Mon, 26 Jul 2004, Matthieu Sozeau wrote:
> On Sun, Jul 25, 2004 at 12:01:03PM -0500, Brian Hurt wrote:
> > On Sun, 25 Jul 2004, Martin Jambon wrote:
> >
> > A better interface might be:
> >
> > val find: (elt -> int) -> t -> elt
>
> Why an int ? Isn't a boolean enough ?
Two reasons:
1) This allows you to use Pervasives.compare (or other compatible
function) partially applied.
2) In addition to equality, you also need less than/greater than in order
to keep the function in O(log N)- which branch do you descend? With just
equality, you need to do an O(N) exhaustive search.
>
> > There is a lot of functionality I'd like to be able to add to map and set.
> > I find myself reimplementing them on a regular basis myself (and no, I
> > haven't thought of a better solution).
>
> Apart from "val of_list : elt list -> t" (a one liner) and the find
> function (a fold with an exception or using `exists` and keeping a
> reference, which indicates, I think, that it should be implemented
> directly in set.ml), i don't remember truly missing functions.
> What are those ?
Map, fold, and iter over pairs of maps or sets is the one I always end up
needing. Also, enums would be nice. Actually, I could do the pairwise
comprehensions if I had enums.
>
> > Many people on this list don't like modules, however.
>
> That seems like a weird opinion to me, and mine is that most OCaml hackers
> are really caml hackers who don't want to know about the OO part.
>
When I tossed out my changes to map and set, they were bounced with a
"they use modules- you should apply them to the demodulized versions of
the code instead". And about the only feed back I ever got on priority
search queues amounted to "it uses modules- we don't like modules".
--
"Usenet is like a herd of performing elephants with diarrhea -- massive,
difficult to redirect, awe-inspiring, entertaining, and a source of
mind-boggling amounts of excrement when you least expect it."
- Gene Spafford
Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-07-26 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 8:17 Martin Jambon
2004-07-25 16:26 ` Matt Gushee
2004-07-25 17:01 ` Brian Hurt
2004-07-26 10:40 ` Matthieu Sozeau
2004-07-26 15:25 ` Brian Hurt [this message]
2004-07-26 15:47 ` Martin Jambon
2004-07-26 16:26 ` Brian Hurt
2004-07-26 7:43 ` Diego Olivier Fernandez Pons
2004-07-26 16:24 ` Martin Jambon
2004-07-26 16:52 ` Diego Olivier Fernandez Pons
2004-07-27 21:45 ` [Caml-list] Camlp4 help/questions Josh Smith
2004-07-27 22:11 ` Brian Hurt
2004-07-28 1:15 ` Josh Smith
[not found] ` <200407272307.50167.jon@jdh30.plus.com>
2004-07-28 1:38 ` Josh Smith
2004-07-28 8:03 ` Pierre Weis
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=Pine.LNX.4.44.0407261016000.6739-100000@localhost.localdomain \
--to=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=mattam@altern.org \
/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