Fix issue with prototype of WeakMap constructor.

Fix issue with prototype of WeakMap constructor.

The WeakMap constructor didn't have a unique prototype, so it shared one with
Object. All WeakMap functions (including "get" and "set") were installed on
that prototype.

R=rossberg@chromium.org
BUG=v8:1617
TEST=mjsunit/harmony/weakmaps

Committed: http://code.google.com/p/v8/source/detail?r=8941

[rossberg, 2011-08-16 11:14:19]

http://codereview.chromium.org/7658008/diff/1/test/mjsunit/harmony/weakmaps.js
File test/mjsunit/harmony/weakmaps.js (right):

http://codereview.chromium.org/7658008/diff/1/test/mjsunit/harmony/weakmaps.j...
test/mjsunit/harmony/weakmaps.js:144: assertFalse(WeakMap.prototype ===
Object.prototype);
Could you also add a couple of tests checking that the usual object stuff works
properly on weak map objects? I.e., setting and getting some properties, through
syntax and through the reflective interface.

[Michael Starzinger, 2011-08-16 11:53:19]

Added new patch set.

http://codereview.chromium.org/7658008/diff/1/test/mjsunit/harmony/weakmaps.js
File test/mjsunit/harmony/weakmaps.js (right):

http://codereview.chromium.org/7658008/diff/1/test/mjsunit/harmony/weakmaps.j...
test/mjsunit/harmony/weakmaps.js:144: assertFalse(WeakMap.prototype ===
Object.prototype);
On 2011/08/16 11:14:19, rossberg wrote:
> Could you also add a couple of tests checking that the usual object stuff
works
> properly on weak map objects? I.e., setting and getting some properties,
through
> syntax and through the reflective interface.

Done.

[rossberg, 2011-08-16 11:58:44]

LGTM