W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2014

Re: WindowProxy as the key in ES6 Set/Map/WeakSet/WeakMap

From: Adam Klein <adamk@chromium.org>
Date: Fri, 18 Apr 2014 10:58:54 -0700
Message-ID: <CAEvLGcKDeVVS3Ym0A4vfX3xkyv5B8uiFu3nKJZCoaQq1f2b_vA@mail.gmail.com>
To: Rick Waldron <waldron.rick@gmail.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, Adam Barth <abarth@chromium.org>, Domenic Denicola <domenic@domenicdenicola.com>, "Mark S. Miller" <erights@google.com>, Toon Verwaest <verwaest@chromium.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Fri, Apr 18, 2014 at 10:08 AM, Rick Waldron <waldron.rick@gmail.com>wrote:
> On Thu, Apr 17, 2014 at 8:14 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> On 4/17/14 6:35 PM, Rick Waldron wrote:
>>> Will this actually matter? Will `w` ever have a _different_ identity
>>> such that it will no longer be usable get the value from the map?
>> In Chrome, yes.  Did you not try my testcase at
>> http://jsfiddle.net/zVqVX/1/ in Chrome?
> I don't know where the disconnect was, but yes I see this result
> now—thanks for your patience.
> @Mark Miller, have you seen this example? Run it in Chrome with
> experimental JS on—the object apparently violates its own identity.

To be clear, I'm actively working on the Map/Set implementations, and
they're flag-guarded, so changing Chrome's behavior is very much on the
table (and it's why I sent this message in the first place).

- Adam
Received on Friday, 18 April 2014 17:59:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:21 UTC