Fix handling of bogus receivers for Harmony collections.

Fix handling of bogus receivers for Harmony collections.

R=rossberg@chromium.org
BUG=v8:1884
TEST=mjsunit/harmony/collections

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

[rossberg, 2012-01-04 10:06:59]

http://codereview.chromium.org/9074003/diff/1/test/mjsunit/harmony/collection...
File test/mjsunit/harmony/collections.js (right):

http://codereview.chromium.org/9074003/diff/1/test/mjsunit/harmony/collection...
test/mjsunit/harmony/collections.js:286: assertThrows(function () {
func.call({}, {}) }, TypeError);
Particularly interesting cases would be variations of:

Map.prototype.get(WeakMap(), {})

etc. (which is what actually triggered this bug report).

[Michael Starzinger, 2012-01-05 10:40:03]

PTAL.

http://codereview.chromium.org/9074003/diff/1/test/mjsunit/harmony/collection...
File test/mjsunit/harmony/collections.js (right):

http://codereview.chromium.org/9074003/diff/1/test/mjsunit/harmony/collection...
test/mjsunit/harmony/collections.js:286: assertThrows(function () {
func.call({}, {}) }, TypeError);
On 2012/01/04 10:07:00, rossberg wrote:
> Particularly interesting cases would be variations of:
> 
> Map.prototype.get(WeakMap(), {})
> 
> etc. (which is what actually triggered this bug report).

Done. I generalized the regression test a bit.

[rossberg, 2012-01-05 12:49:01]

lgtm