For what it’s worth, I have never agreed with this policy. This policy seems to be based on feelings not facts.
I remember implementing real time GCs for Java, which changed GC timing and behavior a lot, and having zero problem getting that aspect of the GC to work well with existing code. It seems like we are using non-problems to make excuses to avoid supporting something useful. In fact, WeakMap is more restrictive constraint on GC algo than weak refs or finalization or whatever, since it means that a Siebert-style fine-grained incremental GC with O(1) increments is off the table. -Filip > On Oct 20, 2017, at 5:59 AM, Domenic Denicola <[email protected]> wrote: > > https://w3ctag.github.io/design-principles/#js-gc > > From: es-discuss [mailto:[email protected]] On Behalf Of Michal > Wadas > Sent: Friday, October 20, 2017 08:07 > To: [email protected] > Subject: Observable GC > > Hi. > > Is there any comprehensive answer about why ability to observe garbage > collection is considered undesirable in JavaScript? > > Michał Wadas > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
