From: Francois Pottier <Francois.Pottier@inria.fr>
To: Dan Grossman <danieljg@cs.cornell.edu>
Cc: caml-list@inria.fr
Subject: Re: Alternative generic hash function
Date: Mon, 29 May 2000 15:13:57 +0200 [thread overview]
Message-ID: <20000529151357.24569@pauillac.inria.fr> (raw)
In-Reply-To: <392ED1F3.A08D283D@cs.cornell.edu>; from Dan Grossman on Fri, May 26, 2000 at 03:35:15PM -0400
Dan,
> Why do you think the overhead would be high?
I was thinking of a recording mutability per-field, rather than
per-object. I agree that your proposal seems economical enough.
> there are plenty of clever tricks you can put in the runtime system
> that exploit the immutability of objects.
Would you care to elaborate? I am no compiler expert, but I'm not sure
why it would be so interesting to have this information at runtime,
where it is already too late to do code optimization. That would allow
implementing the `pure' hash function proposed by Manuel Fähndrich, but
with a cost: the user would have to separate the mutable fields into a
sub-object, so as to allow the root object to be tagged as immutable.
Which other tricks do you have in mind?
--
François Pottier
Francois.Pottier@inria.fr
http://pauillac.inria.fr/~fpottier/
next prev parent reply other threads:[~2000-05-29 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-24 22:04 Manuel Fahndrich
2000-05-25 7:00 ` Pierre Weis
2000-05-25 7:14 ` STARYNKEVITCH Basile
2000-05-25 7:38 ` Dmitri Lomov
2000-05-25 8:24 ` Francois Pottier
2000-05-26 19:35 ` Dan Grossman
2000-05-29 13:13 ` Francois Pottier [this message]
2000-05-29 23:45 ` Ken Wakita
2000-05-30 17:25 ` Dan Grossman
2000-05-25 17:08 Manuel Fahndrich
2000-05-29 15:00 Damien Doligez
2000-05-30 18:04 ` Daniel Ortmann
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=20000529151357.24569@pauillac.inria.fr \
--to=francois.pottier@inria.fr \
--cc=caml-list@inria.fr \
--cc=danieljg@cs.cornell.edu \
/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