From: Leo White <leo@lpw25.net>
To: "Török Edwin" <edwin+ml-ocaml@etorok.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Presumed bug in OCaml's garbage collector or in its Weak module...
Date: Sat, 18 Jun 2016 17:54:59 +0100 [thread overview]
Message-ID: <86eg7ucu8s.fsf@lpw25.net> (raw)
In-Reply-To: <3673db34-9350-a9b1-fcd5-e7593ba0fd01@etorok.net> (=?utf-8?B?IlTDtnLDtms=?= Edwin"'s message of "Fri, 17 Jun 2016 22:41:25 +0300")
> Shallow copies don't seem very safe in the presence of out-of-OCaml-heap C pointers [*].
> Perhaps Weak.get_copy should raise if it encounters a Custom_tag?
Shallow copies aren't even type-safe in the proper sense of the word,
since copying a value of abstract type breaks abstraction. This is why
Obj.dup is in the Obj module. Really Weak.get_copy shouldn't exist, or
should at least be part of Obj not Weak.
I suspect Weak.get_copy only really exists for implementing the weak
hash tables, and even there using it means that you could give Weak.Make
a valid argument whose equal function used `==` and it would give
incorrect results.
Regards,
Leo
next prev parent reply other threads:[~2016-06-18 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 18:09 "Martin R. Neuhäußer"
2016-06-17 19:23 ` Gabriel Scherer
2016-06-18 15:15 ` "Martin R. Neuhäußer"
2016-06-17 19:41 ` Török Edwin
2016-06-17 20:29 ` "Martin R. Neuhäußer"
2016-06-18 10:59 ` Josh Berdine
2016-06-18 15:11 ` "Martin R. Neuhäußer"
2016-06-18 16:54 ` Leo White [this message]
2016-06-21 12:43 ` François Bobot
2016-06-21 19:37 ` Alain Frisch
2016-06-22 8:12 ` François Bobot
2016-06-18 17:39 ` "Martin R. Neuhäußer"
2016-06-21 11:55 ` François Bobot
2016-06-27 11:35 ` AW: " Neuhaeusser, Martin
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=86eg7ucu8s.fsf@lpw25.net \
--to=leo@lpw25.net \
--cc=caml-list@inria.fr \
--cc=edwin+ml-ocaml@etorok.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;
as well as URLs for NNTP newsgroup(s).