ES6: Add support for Map.prototype.forEach and Set.prototype.forEach

src/objects-visiting.h

Index: src/objects-visiting.h
diff --git a/src/objects-visiting.h b/src/objects-visiting.h
index 910334b77c41d8f2d3b795f1de71df08dc751c0a..864a42de5e6888de8fe125472f903e92f816f86e 100644
--- a/src/objects-visiting.h
+++ b/src/objects-visiting.h
@@ -98,6 +98,8 @@ class StaticVisitorBase : public AllStatic {
   V(JSFunction)               \
   V(JSWeakMap)                \
   V(JSWeakSet)                \
+  V(JSMapIterator)            \

[Michael Starzinger, 2014/04/15 16:13:56]

These definitions should not be needed, the two objects behave like normal
JSObjects and don't need any special casing in the visitor.

[arv (Not doing code reviews), 2014/04/15 17:07:23]

Done.

I'll have to re-add them when I expose the iterators to user code.

[Michael Starzinger, 2014/04/15 22:02:30]

These visitor ids are the main reason I asked for a GC test case. Because with
the old version I reviewed (i.e. patch set #8 and #9) the iterator objects got
separate visitor ids assigned but none of the visitors actually registered any
callbacks for these ids. So although I didn't try to run it, I was under the
impression that e.g. the static marking visitor would not have been able to
handle those new visitor ids. I am still pretty convinced that running the new
test against patch set #9 will crash, because it will dispatch to a
non-registered callback.

+  V(JSSetIterator)            \
   V(JSArrayBuffer)            \
   V(JSTypedArray)             \
   V(JSDataView)               \