From: "Till Varoquaux" <till.varoquaux@gmail.com>
To: skaller <skaller@users.sourceforge.net>
Cc: "David Teller" <David.Teller@univ-orleans.fr>,
OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Labelling trees
Date: Fri, 8 Jun 2007 11:52:33 +0200 [thread overview]
Message-ID: <9d3ec8300706080252g788deda5q1ee66a2e2873e6a1@mail.gmail.com> (raw)
In-Reply-To: <1181257757.15201.27.camel@rosella.wigram>
On 6/8/07, skaller <skaller@users.sourceforge.net> wrote:
> On Thu, 2007-06-07 at 16:26 +0200, Till Varoquaux wrote:
> True, but the hash required would be unstable.
>
> Hashing or comparing using the value of a term as a key
> is no good. It's too slow.
Hashing doesn't read the whole structure, it can be parametrized to
read less data. Do you really see a performance boost using addresses
instead?
Regards,
Till
--
http://till-varoquaux.blogspot.com/
next prev parent reply other threads:[~2007-06-08 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 19:43 David Teller
2007-06-06 21:22 ` [Caml-list] " Christophe Raffalli
2007-06-07 1:00 ` skaller
2007-06-07 14:26 ` Till Varoquaux
2007-06-07 23:09 ` skaller
2007-06-08 9:52 ` Till Varoquaux [this message]
2007-06-08 10:32 ` skaller
2007-06-07 14:25 ` Christian Stork
2007-06-07 23:48 ` Jeremy Yallop
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=9d3ec8300706080252g788deda5q1ee66a2e2873e6a1@mail.gmail.com \
--to=till.varoquaux@gmail.com \
--cc=David.Teller@univ-orleans.fr \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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