Index: base/task_scheduler/scheduler_worker.cc |
diff --git a/base/task_scheduler/scheduler_worker.cc b/base/task_scheduler/scheduler_worker.cc |
index 2851a8d43c0948e812bd6d693bded63c43a4d161..d1cc1b1b701064fc4eb34e1300f3ae1382a2c7f6 100644 |
--- a/base/task_scheduler/scheduler_worker.cc |
+++ b/base/task_scheduler/scheduler_worker.cc |
@@ -47,7 +47,7 @@ class SchedulerWorker::Thread : public PlatformThread::Delegate { |
// This is required as SequencedWorkerPool previously blindly CoInitialized |
// all of its threads. |
// TODO: Get rid of this broad COM scope and force tasks that care about a |
- // CoInitialized environment to request one (via an upcoming ExecutionMode). |
+ // CoInitialized environment to request one (via an upcoming trait). |
robliao
2016/10/31 19:19:59
I thought we were keeping COM as an execution mode
fdoray
2016/10/31 19:44:51
From Gab in "Typed TaskRunners and child TaskRunne
robliao
2016/10/31 19:50:46
In the Sequenced+COM case, it would be unexpected
fdoray
2016/10/31 20:42:28
Changed "upcoming trait" to "upcoming execution mo
|
win::ScopedCOMInitializer com_initializer; |
#endif |