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