[base] Make PostTask destination explicit in /chrome/browser/bitmap_fetcher
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=petewil@chromium.org Bug: 1026641 Change-Id: Id676174f093ce32d2cc691ca2deb8415f0b95c0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217203 Auto-Submit: Gabriel Charette <gab@chromium.org> Commit-Queue: Peter Williamson <petewil@chromium.org> Reviewed-by:Peter Williamson <petewil@chromium.org> Cr-Commit-Position: refs/heads/master@{#772287}
Showing
Please register or sign in to comment