Add a use counter API

include/v8.h

Index: include/v8.h
diff --git a/include/v8.h b/include/v8.h
index f6c6ac3cf735e9005ef0ce4ee7a192cc46e0aa89..bc2ea0bb0af5e11e048280667909143dfba2a006 100644
--- a/include/v8.h
+++ b/include/v8.h
@@ -4129,6 +4129,19 @@ class V8_EXPORT Isolate {
   };
 
   /**
+   * Features reported via the SetUseCounterCallback callback. Do not chang

[Sven Panne, 2014/06/23 09:29:39]

+e

+   * assigned numbers of existing items; add new features to the end of this
+   * list.
+   */
+  enum UseCounterFeature {

[Sven Panne, 2014/06/23 09:29:39]

I general, I'm a bit torn how to represent such a bag of random, ad-hoc,
sure-to-be-changed-later things:

   * One could use an enum like this plus a comment like the one above, but at
some point one will reach the state when some enums are not supported anymore,
new ones have to be introduced, etc.

   * One could go the more untyped way of using e.g. strings, which have less
static guarantees, but lead to less API churn.

There are well-known existing API examples in the real world for both variants,
so I really don't know what's better here, let's discuss this offline...

+    kUseAsm = 0
+  };
+
+  typedef void (*UseCounterCallback)(Isolate* isolate,
+                                     UseCounterFeature feature);
+
+
+  /**
    * Creates a new isolate.  Does not change the currently entered
    * isolate.
    *
@@ -4397,6 +4410,11 @@ class V8_EXPORT Isolate {
    */
   bool WillAutorunMicrotasks() const;
 
+  /**
+   * Sets a callback for counting the number of times a feature of V8 is used.
+   */
+  void SetUseCounterCallback(UseCounterCallback callback);
+
  private:
   template<class K, class V, class Traits> friend class PersistentValueMap;