Right, but I guess I tend to automatically look at it in terms of what the amount of exposure is to JSland for guidance in assessing what the magnitude of implementation difficulties will be. I imagine the ways something like the WeakMap gc changes break are ones that are mostly areas where they just don't work efficiently, or don't work at all. Where the ways proxies break ends up with all sorts of crazy elevated access holes.
Although...Firefox sure seems to be on my case a hell of a lot about failing to preserve wrappers for wrapper native weak map keys. On Tue, May 29, 2012 at 10:22 AM, Allen Wirfs-Brock <[email protected]>wrote: > > On May 29, 2012, at 7:19 AM, Brandon Benvie wrote: > > > Proxies have a huge surface area to them, not to mention a whole new > updated specification with some significant core differences, so I don't > blame you for that. On the other hand WeakMaps have a tiny surface area are > super useful... ;) > > WeakMaps require a major change to any implementations garbage > collector.... > > Allen > > > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
