From: Damien Doligez <damien.doligez@inria.fr>
To: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Weak array semantics with mutually recursive values.
Date: Mon, 24 Jan 2011 13:45:26 +0100 [thread overview]
Message-ID: <5E60A32A-4DAB-4870-AD8F-20080071B81B@inria.fr> (raw)
In-Reply-To: <4D3B05E6.3090103@univ-savoie.fr>
On 2011-01-22, at 17:29, Christophe Raffalli wrote:
> for instance. They will become unreachable by the GC at the same cycle.
> However,
> if they are both added in a weak array, it seems that they may not be
> removed at the same time from the array.
>
> I have some code that seems to show that most of the time they are
> removed at the same times, but very rarely this fails.
As far as I can tell, it should never happen. Do you have a good
repro case?
-- Damien
next prev parent reply other threads:[~2011-01-24 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 16:29 Christophe Raffalli
[not found] ` <4d3b1a5d.ccefd80a.600d.177e@mx.google.com>
2011-01-22 19:41 ` Christophe Raffalli
2011-01-24 12:45 ` Damien Doligez [this message]
2011-01-24 21:41 ` Christophe Raffalli
2011-01-26 13:13 ` Damien Doligez
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=5E60A32A-4DAB-4870-AD8F-20080071B81B@inria.fr \
--to=damien.doligez@inria.fr \
--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