From: oliver@first.in-berlin.de (Oliver Bandel)
To: caml-list@inria.fr
Subject: Re: [oliver: Re: [Caml-list] Should be INSIDE STANDARD-LIB: Hashtbl.keys]
Date: Sat, 24 Apr 2004 12:39:44 +0200 [thread overview]
Message-ID: <20040424103944.GF1336@first.in-berlin.de> (raw)
In-Reply-To: <200404240546.17082.jdh30@cam.ac.uk>
On Sat, Apr 24, 2004 at 05:46:17AM +0100, Jon Harrop wrote:
> On Saturday 24 April 2004 4:00 am, skaller wrote:
> > On Sat, 2004-04-24 at 06:09, Oliver Bandel wrote:
> > > Because there is no Hashtbl.size in the standard lib,
> >
> > which sux because O(n) is a high price to pay
> > for an integer the Hashtbl could keep track of
> > easily.
>
> I don't want the overhead of hash tables carrying around and updating an int.
> I was miffed when they put an O(1) criterion on length() in the STL "list" in
> C++...
>
OK, if it is too much performance critical, then forget the idea with
the counter.
So Hashtbl.size should be done with Hashtbl.iter and incrementing
a counter-ref then.
But maybe it nevertheless makes sense to put it inside the
Hashtbl-module. (But not necissarily.)
Ciao,
Oliver
-------------------
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-04-24 11:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 20:09 Oliver Bandel
2004-04-24 3:00 ` skaller
2004-04-24 4:46 ` Jon Harrop
2004-04-24 10:39 ` Oliver Bandel [this message]
2004-04-25 18:54 ` Marcin 'Qrczak' Kowalczyk
2004-04-25 20:06 ` Jon Harrop
2004-04-26 10:14 ` Richard Jones
2004-04-26 17:13 ` Jon Harrop
2004-04-24 6:42 ` Basile STARYNKEVITCH
2004-04-24 19:12 ` skaller
2004-04-24 8:56 ` Oliver Bandel
2004-04-23 20:09 Oliver Bandel
2004-04-23 20:09 Oliver Bandel
2004-04-23 20:10 Oliver Bandel
2004-04-23 20:10 Oliver Bandel
2004-04-24 7:30 ` Martin Jambon
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=20040424103944.GF1336@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
/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