As discussed @ https://groups.google.com/a/chromium.org/d/msg/chromium-dev/mXarHTy5Drg/oSuiABZwDAAJ
It is more and more important as things move to sequences and pools that this method's name be addressed (I just found myself writing unintuitive code because of this).
I suggest we:
1) Define TaskRunner::RunsTasksInCurrentSequence()
2) Make TaskRunner::RunsTasksOnCurrentThread() non-virtual and define it in task_runner.cc in terms of TaskRunner::RunsTasksInCurrentSequence().
(2) will force us to fix the overrides to be in terms of RunsTasksInCurrentSequence() and as such make sure every impl is already doing the right thing.
(2) will allow us to do this without having to also rename callers and having important changes lost in the rename noise.
3) Mass rename for callers.
@fdoray for triage : this would be a good bug to start ramping someone new on our team :), potentially followed by more exciting migration work in base/ towards making APIs sequence-safe :).
Comment 1 by cmorehun...@gmail.com
, Nov 24 2016