Expose a way to make a "same-origin" realm

src/d8.h

Index: src/d8.h
diff --git a/src/d8.h b/src/d8.h
index e51e8ee13fae98b3bcc7b3d3fab5421548213454..028c55179d0b5e78115925a5e7434aae54f97307 100644
--- a/src/d8.h
+++ b/src/d8.h
@@ -375,6 +375,8 @@ class Shell : public i::AllStatic {
   static void RealmOwner(const v8::FunctionCallbackInfo<v8::Value>& args);
   static void RealmGlobal(const v8::FunctionCallbackInfo<v8::Value>& args);
   static void RealmCreate(const v8::FunctionCallbackInfo<v8::Value>& args);
+  static void RealmMakeSameOrigin(

[adamk, 2016/05/13 23:09:59]

Taking a different-origin realm and making it same-origin seems a little funny
to me. What if you instead add a new kind of creation? RealmCreateSameOrigin,
perhaps? Or an extra argument to Create?

Naming: "Origin" is unfortunately a web concept and not a JS concept. It's
mentioned in passing in the API, but I wonder if there's something better we
could use. "RealmCreateAllowCrossRealmAccess" seems really long, but I think we
should think on this. Whatever name we use here is likely to be treated as part
of our API.

[rossberg, 2016/05/18 07:23:52]

+1

+      const v8::FunctionCallbackInfo<v8::Value>& args);
   static void RealmDispose(const v8::FunctionCallbackInfo<v8::Value>& args);
   static void RealmSwitch(const v8::FunctionCallbackInfo<v8::Value>& args);
   static void RealmEval(const v8::FunctionCallbackInfo<v8::Value>& args);