caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Should be INSIDE STANDARD-LIB: Hashtbl.keys
Date: Fri, 23 Apr 2004 14:51:41 +0200	[thread overview]
Message-ID: <20040423145141.B3686@pauillac.inria.fr> (raw)
In-Reply-To: <20040421011904.GA1411@first.in-berlin.de>; from oliver@first.in-berlin.de on Wed, Apr 21, 2004 at 03:19:04AM +0200

> I think a good addition to the Hashtbl-module
> would be a function, that gives back a list of keys
> that are in the hash.

With your specification (no repetitions in the list), that function
would run in quadratic time, which is a sure sign that lists aren't
the right data structure here.  (More generally speaking, "lists
without repetitions" is almost always the wrong data structure.)

If you shoot for decent efficiency, you have two choices: 1- a list of
keys with possible repetitions, and 2- a set of keys.
1- is linear-time but rarely useful.  2- requires a suitable set
module over the keys, and thus can't be done inside the Hashtbl library.

As you see, there is no single "good" behavior and interface for the
function you outline.  (For another example, refer to the discussion
about String.map earlier on this list; every poster had their own
ideas about what type it should have.)  That's a sign that it doesn't
belong in the standard library, and you should program the behavior
that you need in your application using Hashtbl.fold.

- Xavier Leroy

-------------------
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


  parent reply	other threads:[~2004-04-23 12:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  1:19 Oliver Bandel
2004-04-21  8:39 ` Richard Jones
2004-04-21  9:13 ` Martin Jambon
2004-04-23 12:51 ` Xavier Leroy [this message]
2004-04-23 13:05   ` Jean-Baptiste Rouquier
2004-04-23 16:04     ` Xavier Leroy
2004-04-23 18:21       ` Jon Harrop
2004-04-23 21:31         ` Jon Harrop
2004-04-23 21:53           ` John Goerzen
2004-04-26  6:28           ` Florian Hars
2004-04-23 18:29       ` John Goerzen
     [not found]         ` <20040423190710.GA1506@first.in-berlin.de>
2004-04-23 20:42           ` John Goerzen
2004-04-23 15:03   ` Richard Jones
2004-04-24  1:58     ` skaller
2004-04-24  9:20       ` Nicolas Cannasse
2004-04-24 19:26         ` skaller
2004-04-26  7:29       ` Jean-Christophe Filliatre
2004-04-23 16:06   ` Brian Hurt
2004-04-23 16:31     ` Martin Jambon
2004-04-23 17:27     ` Christoph Bauer
2004-04-23 18:29   ` John Goerzen
     [not found]     ` <20040423191010.GB1506@first.in-berlin.de>
2004-04-23 20:41       ` John Goerzen
     [not found]         ` <20040424080904.GA821@first.in-berlin.de>
2004-04-24 20:59           ` John Goerzen
2004-04-25  8:12             ` Oliver Bandel
2004-04-23 18:28 ` John Goerzen

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=20040423145141.B3686@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=oliver@first.in-berlin.de \
    /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).