Migrate MessageLoop::current() to MessageLoopCurrent in /mojo
These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.
Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.
The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).
As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.
Possible script screw ups / things to look out for in this review:
- Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
one (I will go over that in a separate pass).
Includes should have been stripped if that was the last usage of message_loop.h
in that file.
Please CQ if LGTY
This CL was uploaded by git cl split.
R=sky@chromium.org
Bug: 825327
Change-Id: Ieae521d62d35bae3cd5c54309796f2b0c702679c
Reviewed-on: https://chromium-review.googlesource.com/1024378
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553454}
CrOS-Libchrome-Original-Commit: 32044bca2d8effbc75a2bf2cfa98a49aaebdbd8c
6 files changed