Expose performance.memory in workers

public/web/WebWorkerSettings.h

+// Copyright 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef WebWorkerSettings_h
+#define WebWorkerSettings_h
+
+#include "public/platform/WebCommon.h"
+#include "public/platform/WebPrivateOwnPtr.h"
+
+namespace WebCore {
+class WorkerSettings;
+}
+
+#if BLINK_IMPLEMENTATION
+namespace WTF { template <typename T> class PassOwnPtr; }
+#endif
+
+namespace blink {
+
+// WebWorkerSettings is owned by the WebSharedWorker, and allows code to
+// modify the settings for the WebSharedWorker.

[kinuko, 2014/03/10 05:55:52]

This comment looks wrong now?

+class WebWorkerSettings {
+public:
+    ~WebWorkerSettings() { reset(); }
+
+    WebWorkerSettings(const WebWorkerSettings& n) { assign(n); }
+
+    WebWorkerSettings& operator=(const WebWorkerSettings& n)
+    {
+        assign(n);
+        return *this;
+    }
+
+    BLINK_EXPORT static WebWorkerSettings create();
+    BLINK_EXPORT void reset();
+    BLINK_EXPORT void assign(const WebWorkerSettings&);
+
+    BLINK_EXPORT void setMemoryInfoEnabled(bool);

[abarth-chromium, 2014/03/10 21:32:36]

Does this setting need to be per-worker?  Do we not want to use a per-process
setting?

[abarth-chromium, 2014/03/10 21:33:29]

If this maps to a command-line flag in Chromium, it sounds like this would be
better as a per-process runtime-enabled feature.

+
+#if BLINK_IMPLEMENTATION
+    WebWorkerSettings(const WTF::PassOwnPtr<WebCore::WorkerSettings>&);
+    operator WTF::PassOwnPtr<WebCore::WorkerSettings>() const;
+#endif
+
+private:
+    WebPrivateOwnPtr<WebCore::WorkerSettings> m_private;
+};
+
+} // namespace blink
+
+#endif