From: "Ohad Rodeh" <ORODEH@il.ibm.com>
To: caml-list@inria.fr
Subject: [Caml-list] mutability analysis too strict?
Date: Sun, 9 Dec 2001 17:43:41 +0200 [thread overview]
Message-ID: <OF80DB041C.5AFDD811-ONC2256B1D.00560066@telaviv.ibm.com> (raw)
List,
I have a problem with hashtable mutability analysis. For example:
let h = Hashtbl.create 10;;
h : ('_a, '_b) Hashtbl.t
The objects and keys in the table are infered to be mutable. However,
in my case, they are immutable and I have to coerce them using Obj.magic
from
'_b to 'b.
Can this be fixed? why is the analysis so restrictive?
Ohad.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2001-12-10 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 15:43 Ohad Rodeh [this message]
2001-12-10 8:13 ` Francois Pottier
-- strict thread matches above, loose matches on Subject: below --
2001-12-10 10:13 Ohad Rodeh
2001-12-10 10:30 ` Basile STARYNKEVITCH
2001-12-10 10:50 ` Francois Pottier
2001-12-10 11:21 ` Mark Seaborn
2001-12-10 9:12 Ohad Rodeh
2001-12-10 9:28 ` Remi VANICAT
2001-12-09 12:14 [Caml-list] Mutability " Ohad Rodeh
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=OF80DB041C.5AFDD811-ONC2256B1D.00560066@telaviv.ibm.com \
--to=orodeh@il.ibm.com \
--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