From: oliver@first.in-berlin.de (Oliver Bandel)
To: caml-list@inria.fr
Subject: Re: [Caml-list] Should be INSIDE STANDARD-LIB: Hashtbl.keys
Date: Sun, 25 Apr 2004 10:12:00 +0200 [thread overview]
Message-ID: <20040425081200.GB762@first.in-berlin.de> (raw)
In-Reply-To: <20040424205936.GE29097@complete.org>
On Sat, Apr 24, 2004 at 03:59:36PM -0500, John Goerzen wrote:
> On Sat, Apr 24, 2004 at 10:09:04AM +0200, Oliver Bandel wrote:
> > On Fri, Apr 23, 2004 at 03:41:49PM -0500, John Goerzen wrote:
> > > OK, but why should we eliminate a useful function because 1% of uses
> > > of it will be slow?
> > >
> > > Make a note in the docs (like that notes that are there already that say
> > > "this function is not tail-recursive") and put it in for those that will
> > > find it useful.
> >
> >
> > What does the O()-notation have to do with tail recursiveness?
> > IMHO nothing. But I'm not a computer scientist. Maybe there
> > is a linkage between. But the O()-notation says something about the
>
> What I'm saying is this: a known problem with a function, whether it is
> excessive stack use or slow performance, is not necessarily a reason to
> keep it out of the standard library. The flaw should be noted in the
> documentation. And that's just what has been done with the
> non-tail-recursive functions.
OK, I see and I agree with that.
Nevertheless everybody is interested to have best stuff inside
the lib, which is possible.
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-25 9:00 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
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 [this message]
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=20040425081200.GB762@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