A first skeleton for introducing Harmony proxies

src/objects-visiting.cc

Index: src/objects-visiting.cc
diff --git a/src/objects-visiting.cc b/src/objects-visiting.cc
index bcb48ea5a8abccccfb858fe6866a08584fc30e8f..eab864b12de10b89553a0856acf9f58dfa5a52d5 100644
--- a/src/objects-visiting.cc
+++ b/src/objects-visiting.cc
@@ -88,6 +88,11 @@ StaticVisitorBase::VisitorId StaticVisitorBase::GetVisitorId(
     case SHARED_FUNCTION_INFO_TYPE:
       return kVisitSharedFunctionInfo;
 
+    case JS_PROXY_TYPE:
+      return GetVisitorIdForSize(kVisitDataObject,

[Vyacheslav Egorov (Chromium), 2011/05/22 14:45:50]

This introduces a subtle GC problem: JS_PROXY is not a data object. Data objects
do not contain pointers in their bodies.

We should either pretend that JS_PROXY is a struct (kVisitStruct,
kVisitStructGeneric) or introduce a separate kVisitJSProxy. 

I think pretending that JS_PROXY is a struct should be fine especially because
proxies are probably not going to need any special handling by visitors.

[rossberg, 2011/05/23 08:45:28]

Done.

+                                 kVisitDataObjectGeneric,
+                                 JSProxy::kSize);
+
     case PROXY_TYPE:
       return GetVisitorIdForSize(kVisitDataObject,
                                  kVisitDataObjectGeneric,