Do not inherit TaskPriority in TaskTraits.

base/task_scheduler/test_utils.h

 // Copyright 2016 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 BASE_TASK_SCHEDULER_TEST_UTILS_H_
 #define BASE_TASK_SCHEDULER_TEST_UTILS_H_
 
+#include "base/task_scheduler/task_traits.h"
+
 namespace base {
 namespace internal {
 namespace test {
 
 // An enumeration of possible task scheduler TaskRunner types. Used to
 // parametrize relevant task_scheduler tests.
 enum class ExecutionMode { PARALLEL, SEQUENCED, SINGLE_THREADED };
 
+// Returns TaskTraits with a non-INHERITED priority. This is useful because it
+// is invalid to initialize a Task with TaskTraits whose priority is INHERITED.
+TaskTraits CreateTaskTraits();

[gab, 2017/04/25 14:19:16]

Can we instead hold a const bitfield in TaskTraits of which traits were
specified explicitly? post_task.cc can then decide to replace those that weren't
with inherited properties where that makes sense.

I think that (1) scales better (2) is less intrusive and (3) avoids forcing an
undesired "beyond max" value to be handled by switches/etc.

[fdoray, 2017/04/25 15:21:19]

Done.

+
 }  // namespace test
 }  // namespace internal
 }  // namespace base
 
 #endif  // BASE_TASK_SCHEDULER_TEST_UTILS_H_