Sequence[d]TaskRunner

docs/threading_and_tasks.md

 # Threading and Tasks in Chrome
 
 [TOC]
 
 ## Overview
 
 ### Threads
 
 Every Chrome process has
 
@@ skipping 638 matching lines @@
 
 Dependency injection of TaskRunners can still seldomly be useful to unit test a
 component when triggering a specific race in a specific way is essential to the
 test. For such cases the preferred approach is the following:
 
 ```cpp
 class FooWithCustomizableTaskRunnerForTesting {
  public:
 
   void SetBackgroundTaskRunnerForTesting(
-      scoped_refptr<base::SequenceTaskRunner> background_task_runner);
+      scoped_refptr<base::SequencedTaskRunner> background_task_runner);
 
  private:
-  scoped_refptr<base::SequenceTaskRunner> background_task_runner_ =
-      base::CreateSequenceTaskRunnerWithTraits(
+  scoped_refptr<base::SequencedTaskRunner> background_task_runner_ =
+      base::CreateSequencedTaskRunnerWithTraits(
           {base::MayBlock(), base::TaskPriority::BACKGROUND});
 }
 ```
 
 Note that this still allows removing all layers of plumbing between //chrome and
 that component since unit tests will use the leaf layer directly.