Getting rid of DelegatedFrameData

cc/output/compositor_frame.cc

 // Copyright 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "cc/output/compositor_frame.h"
 
 namespace cc {
 
 CompositorFrame::CompositorFrame() {}
 
 CompositorFrame::CompositorFrame(CompositorFrame&& other) = default;
 
 CompositorFrame::~CompositorFrame() {}
 
 CompositorFrame& CompositorFrame::operator=(CompositorFrame&& other) = default;
 
+bool CompositorFrame::IsEmpty() const {
+  return render_pass_list.empty() && resource_list.empty();

[danakj, 2016/10/25 22:23:07]

I find this function weird..

1) resource_list is a set of things referred to in the render_pass_list. So it
has to be empty if render_pass_list is empty.

2) empty compositor frames exist before this patch and we don't branch on them
in places that this patch now does, so why is that what we want?

[Fady Samuel, 2016/10/26 03:13:55]

I agree we probably don't need this or just return render_pass_list.empty() and
DCHECK that resource_list.empty()) || !render_pass_list.empty()

[Saman Sami, 2016/10/26 14:41:18]

1) I'll fix it.
2) There are certain places that we check for empty frames. See
content/browser/android/synchronous_compositor_host.cc:146 for an example. Can
you be more specific about where I have introduced new branches? 

+}
+
 }  // namespace cc