From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Obj.magic and existential types.
Date: Mon, 22 Jun 2009 02:03:45 +0200 [thread overview]
Message-ID: <E83DCC27-418A-4DF4-8292-7C73ABEEB615@erratique.ch> (raw)
In-Reply-To: <c7e4e9f0906211108u5d636f50nb2589943cda214ba@mail.gmail.com>
Le 21 juin 09 à 20:08, Jake Donham a écrit :
> I have not tried either, but from a cursory glance at the code I
> have the impression that React's space safety relies on support for
> weak references, which standard Javascript does not have.
Yes.
The weak module is available in obrowser, but I don't know if it
implements its semantics. If the author of obrowser is on this list
would he be kind enough to enlight us ?
> Leaks memory, yes in your example, but in a less contrived usage,
> where dead references are underneath a bind,
Does that mean the only values froc knows how to garbage collect are
those values that are dynamically created in an update cycle and not
used further ? (because that's rather contrived IMHO)
While excessive in allocation rate the example I gave is not that
contrived e.g. the same pattern occurs naturally in the terminal
breakout game present in react's distribution : each time a new game
starts a record of signals is created to manage the simulation and
game logic and these signals need to be eventually gc'd when the game
is over.
Best,
Daniel
next prev parent reply other threads:[~2009-06-22 0:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 17:42 Guillaume Yziquel
2009-06-19 18:21 ` Daniel Bünzli
2009-06-19 18:30 ` Guillaume Yziquel
2009-06-19 18:37 ` Daniel Bünzli
2009-06-19 18:47 ` [Caml-list] " Jake Donham
2009-06-20 8:30 ` Daniel Bünzli
2009-06-21 18:08 ` Jake Donham
2009-06-21 18:39 ` Yaron Minsky
2009-06-22 0:03 ` Daniel Bünzli [this message]
2009-06-22 9:19 ` Benjamin Canou
2009-06-22 17:02 ` Jake Donham
2009-06-23 0:24 ` Daniel Bünzli
2009-06-23 0:34 ` Jake Donham
2009-06-23 2:22 ` Jake Donham
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=E83DCC27-418A-4DF4-8292-7C73ABEEB615@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--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