Replace init_cb in Renderer::Initialize() with base::Closure.

media/base/renderer.h

Index: media/base/renderer.h
diff --git a/media/base/renderer.h b/media/base/renderer.h
index adb0de7e1333305aca815bee6bb25f915fd1d895..0034bf985f6df36856844d6a4fd66f11619d2b10 100644
--- a/media/base/renderer.h
+++ b/media/base/renderer.h
@@ -25,15 +25,15 @@ class MEDIA_EXPORT Renderer {
   virtual ~Renderer();
 
   // Initializes the Renderer, executing |init_cb| upon completion.
+  // If initialization failed, fires |error_cb| before |init_cb|.
   // TODO(xhwang): Provide a set of DemuxerStreams in Initialize().
-  // TODO(xhwang): Replace |init_cb| with a Closure.
   //
   // Permanent callbacks:
   // - |statistics_cb|: Executed periodically with rendering statistics.
   // - |time_cb|: Executed whenever time has advanced through rendering.
   // - |ended_cb|: Executed when rendering has reached the end of stream.
   // - |error_cb|: Executed if any error was encountered during rendering.
-  virtual void Initialize(const PipelineStatusCB& init_cb,
+  virtual void Initialize(const base::Closure& init_cb,

[tim (not reviewing), 2014/09/03 22:37:26]

How important is it to return PIPELINE_ERROR_INITIALIZATION_FAILED if init
fails? e.g, In a case like I have at https://codereview.chromium.org/518163003,
it was easy before this CL to return that error code without having to add extra
state to my RendererImpl.

[xhwang, 2014/09/03 23:52:37]

I don't quite follow the question.

In you CL, you'll need to plumb in the error_cb_ to your remote_renderer_ (for
other failure cases, e.g. flush error, decoding error). Then you can basically
follow the same model: when init fails, call error_cb first, then fire the
completion callback.

Does that answer your question?

                           const StatisticsCB& statistics_cb,
                           const base::Closure& ended_cb,
                           const PipelineStatusCB& error_cb,