base: Remove most uses of MessageLoopProxy

base/single_thread_task_runner.h

Index: base/single_thread_task_runner.h
diff --git a/base/single_thread_task_runner.h b/base/single_thread_task_runner.h
index b5311db16942f1fe7d791ea454104cc3eccbadb4..ed5bda8f0ad7aff04a4ef7bc30609f1c2e59bf69 100644
--- a/base/single_thread_task_runner.h
+++ b/base/single_thread_task_runner.h
@@ -16,7 +16,7 @@ namespace base {
 // there is a specific need to run tasks on only a single thread.
 //
 // SingleThreadTaskRunner implementations might:
-//   - Post tasks to an existing thread's MessageLoop (see MessageLoopProxy).
+//   - Post tasks to an existing thread's MessageLoop.

[danakj, 2015/04/21 20:16:30]

Is there maybe somewhere else you could refer to here for more info?

[Sami, 2015/04/23 17:48:24]

Good point, MessageLoop::task_runner() is probably the best reference.

 //   - Create their own worker thread and MessageLoop to post tasks to.
 //   - Add tasks to a FIFO and signal to a non-MessageLoop thread for them to
 //     be processed. This allows TaskRunner-oriented code run on threads