scheduler: Move the Blink scheduler into Blink

third_party/WebKit/Source/platform/scheduler/base/enqueue_order.h

 // Copyright 2015 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 COMPONENTS_SCHEDULER_BASE_ENQUEUE_ORDER_H_
-#define COMPONENTS_SCHEDULER_BASE_ENQUEUE_ORDER_H_
+#ifndef THIRD_PARTY_WEBKIT_SOURCE_PLATFORM_SCHEDULER_BASE_ENQUEUE_ORDER_H_
+#define THIRD_PARTY_WEBKIT_SOURCE_PLATFORM_SCHEDULER_BASE_ENQUEUE_ORDER_H_
 
 #include <stdint.h>
 
 #include "base/synchronization/lock.h"
 
+namespace blink {
 namespace scheduler {
 namespace internal {

[haraken, 2016/08/04 01:11:38]

I'm not sure if we need to add the blink namespace. The three level of nesting
(blink => scheduler => internal) looks a bit too verbose to me.

[Sami, 2016/08/04 10:12:41]

These things are internal to the "base" part of the scheduler and because all
things referring to them are already in the blink::scheduler namespace, we never
use the full blink::scheduler::internal notation but instead just internal::*.
Does that alleviate your concern?

I'm not sure what the alternative would be. I wouldn't want to move internal
things to the scheduler namespace since other code might accidentally use them.
Leaving out blink would also be awkward since now we'd have two different
scheduler namespaces (one in blink:: and one in the global scope).

 
 using EnqueueOrder = uint64_t;
 
 class EnqueueOrderGenerator {
  public:
   EnqueueOrderGenerator();
   ~EnqueueOrderGenerator();
 
   EnqueueOrder GenerateNext();
 
  private:
   base::Lock lock_;
   EnqueueOrder enqueue_order_;
 };
 
 }  // namespace internal
 }  // namespace scheduler
+}  // namespace blink
 
-#endif  // COMPONENTS_SCHEDULER_BASE_ENQUEUE_ORDER_H_
+#endif  // THIRD_PARTY_WEBKIT_SOURCE_PLATFORM_SCHEDULER_BASE_ENQUEUE_ORDER_H_