[base] Make PostTask destination explicit in...
[base] Make PostTask destination explicit in /content/public/test/browser_task_environment_unittest.cc Task APIs v3 will all have an explicit destination. In the past "default traits" meant ThreadPool. These CLs are thus a no-op except for the few callers that clearly wanted to post a QuitClosure() on the current thread (posting a QuitClosure() to a parallel task will merely bounce it back to the current thread anyways). Those few callers were migrated to ThreadTaskRunnerHandle::Get(). These changes are thus required to phase out task APIs v2 (post_task.h) Design doc: https://docs.google.com/document/d/1tssusPykvx3g0gvbvU4HxGyn3MjJlIylnsH13-Tv6s4/edit This specific change is a subset of https://chromium-review.googlesource.com/c/chromium/src/+/2216733 This CL was uploaded by git cl split. R=sky@chromium.org Bug: 1026641 Change-Id: I87ec188abf4b2e6a359d69409a74bbf90674197c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215918 Auto-Submit: Gabriel Charette <gab@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#772277}
Showing
Please register or sign in to comment