Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 97642 Enable JavaScript WeakMap
Starred by 26 users Project Member Reported by arv@chromium.org, Sep 22 2011 Back to list
Status: Fixed
Owner:
Closed: Jun 2014
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment
The WeakMap implementation in V8 is now finished

http://code.google.com/p/v8/issues/detail?id=1565&#makechanges

We should enable it in Chromium too.

WeakMap was enabled in Firefox 6.

https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/WeakMap
 
Comment 1 by danno@chromium.org, Oct 18 2011
I think it's premature to enable the flag by default. It's prudent to wait at least until the feature shows up in the ES.next specification working draft and until it has cooked enough so that we don't encourage folks to write code that will later break. There are also still some open issues with the WeakMap implementation (as with all of our Harmony support right now).
Comment 2 by kareng@google.com, Apr 5 2012
Status: Available
Project Member Comment 3 by bugdroid1@chromium.org, Mar 10 2013
Labels: -Area-WebKit -WebKit-JavaScript Cr-Content-JavaScript Cr-Content
Project Member Comment 4 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content Cr-Blink
Project Member Comment 5 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content-JavaScript Cr-Blink-JavaScript
And it is now on WebKit:
https://bugs.webkit.org/show_bug.cgi?id=120912
Isn't this done now?
Cc: -rossberg@chromium.org
Owner: rossberg@chromium.org
Status: Fixed
Which milestone?
Sign in to add a comment