From: Thomas Fischbacher <Thomas.Fischbacher@Physik.Uni-Muenchen.DE>
To: caml-list@inria.fr
Subject: [Caml-list] Hashtbl and destructive operations on keys
Date: Mon, 22 Mar 2004 19:16:57 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0403221904350.9046@seekar.cip.physik.uni-muenchen.de> (raw)
Dear ocaml hackers,
I read the documentation in such a way that I must not assume that after
doing a Hashtbl.replace hash key new_val, I can destructively modify key
with impunity. (I do cons a new key at every Hashtbl.add.)
On the other hand (I have not looked into the sources), I am quite
confident that the system _could_ give me the guarantee that
nothing evil happens if I do so, and especially for the application I am
presently working on, this would induce a noticeable performance gain,
due to reduced consing. (And performance is important here!)
So, could I please get this officially sanctioned? :-)
--
regards, tf@cip.physik.uni-muenchen.de (o_
Thomas Fischbacher - http://www.cip.physik.uni-muenchen.de/~tf //\
(lambda (n) ((lambda (p q r) (p p q r)) (lambda (g x y) V_/_
(if (= x 0) y (g g (- x 1) (* x y)))) n 1)) (Debian GNU)
-------------------
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 reply other threads:[~2004-03-22 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 18:16 Thomas Fischbacher [this message]
2004-03-22 19:09 ` Remi Vanicat
2004-03-22 23:13 ` Thomas Fischbacher
2004-03-23 0:59 ` Jacques Garrigue
2004-03-23 9:20 ` Correnson Loïc
2004-03-23 12:12 ` Thomas Fischbacher
2004-03-23 9:45 ` Oliver Bandel
2004-03-22 23:44 Oliver Bandel
2004-03-22 23:44 Oliver Bandel
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=Pine.LNX.4.58.0403221904350.9046@seekar.cip.physik.uni-muenchen.de \
--to=thomas.fischbacher@physik.uni-muenchen.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