Use ThreadTaskRunnerHandle instead of MessageLoop::current() in base/.

Use ThreadTaskRunnerHandle instead of MessageLoop::current() in base/.

This CL replaces some uses of MessageLoop::current() with
ThreadTaskRunnerHandle in base/.

Why? The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads are migrated to
base/task_scheduler, tasks will no longer have access to a MessageLoop
but they will be able to get the current ThreadTaskRunnerHandle.

BUG=616447
Committed: https://crrev.com/270460f567927f16ea93741f28088a433280bc8c
Cr-Commit-Position: refs/heads/master@{#399711}

[fdoray, 2016-06-13 21:16:18]

fdoray@chromium.org changed reviewers:
+ danakj@chromium.org

[fdoray, 2016-06-13 21:16:19]

Can you review this CL? Thanks.

[danakj, 2016-06-13 21:21:13]

LGTM

https://codereview.chromium.org/2061903002/diff/1/base/process/kill_win.cc
File base/process/kill_win.cc (right):

https://codereview.chromium.org/2061903002/diff/1/base/process/kill_win.cc#ne...
base/process/kill_win.cc:49: // win::ObjectWatcher::Delegate
---------------------------------------------
Heh this is a weird comment. Can you just change it to:

// win::ObjectWatcher::Delegate implementation.

[fdoray, 2016-06-14 14:01:27]

https://codereview.chromium.org/2061903002/diff/1/base/process/kill_win.cc
File base/process/kill_win.cc (right):

https://codereview.chromium.org/2061903002/diff/1/base/process/kill_win.cc#ne...
base/process/kill_win.cc:49: // win::ObjectWatcher::Delegate
---------------------------------------------
On 2016/06/13 21:21:12, danakj wrote:
> Heh this is a weird comment. Can you just change it to:
> 
> // win::ObjectWatcher::Delegate implementation.
> 

Done.

[fdoray, 2016-06-14 14:01:36]

The CQ bit was checked by fdoray@chromium.org

[fdoray, 2016-06-14 14:01:37]

The patchset sent to the CQ was uploaded after l-g-t-m from danakj@chromium.org
Link to the patchset: https://codereview.chromium.org/2061903002/#ps20001
(title: "CR danakj")

[commit-bot: I haz the power, 2016-06-14 14:02:04]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2061903002/20001

[commit-bot: I haz the power, 2016-06-14 15:21:44]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-06-14 15:52:11]

Description was changed from

==========
Use ThreadTaskRunnerHandle instead of MessageLoop::current() in base/.

This CL replaces some uses of MessageLoop::current() with
ThreadTaskRunnerHandle in base/.

Why? The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads are migrated to
base/task_scheduler, tasks will no longer have access to a MessageLoop
but they will be able to get the current ThreadTaskRunnerHandle.

BUG=616447
==========

to

==========
Use ThreadTaskRunnerHandle instead of MessageLoop::current() in base/.

This CL replaces some uses of MessageLoop::current() with
ThreadTaskRunnerHandle in base/.

Why? The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads are migrated to
base/task_scheduler, tasks will no longer have access to a MessageLoop
but they will be able to get the current ThreadTaskRunnerHandle.

BUG=616447

Committed: https://crrev.com/270460f567927f16ea93741f28088a433280bc8c
Cr-Commit-Position: refs/heads/master@{#399711}
==========

[commit-bot: I haz the power, 2016-06-14 15:52:12]

Patchset 2 (id:??) landed as
https://crrev.com/270460f567927f16ea93741f28088a433280bc8c
Cr-Commit-Position: refs/heads/master@{#399711}