Cosmetic cleanup to texture_layer mailboxes.

cc/texture_mailbox.h

Index: cc/texture_mailbox.h
diff --git a/cc/texture_mailbox.h b/cc/texture_mailbox.h
new file mode 100644
index 0000000000000000000000000000000000000000..fda8db4a87c4c250601bebf1f6d4a61c2d727b54
--- /dev/null
+++ b/cc/texture_mailbox.h
@@ -0,0 +1,35 @@
+// Copyright 2013 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.
+
+#ifndef CC_TEXTURE_MAILBOX_H_
+#define CC_TEXTURE_MAILBOX_H_
+
+#include <string>
+
+#include "base/basictypes.h"
+#include "base/callback.h"
+#include "cc/cc_export.h"
+
+namespace cc {
+
+class CC_EXPORT TextureMailbox {
+ public:
+  typedef base::Callback<void(unsigned)> ReleaseCallback;
+  TextureMailbox();
+  TextureMailbox(const std::string& name,
+                 const ReleaseCallback& callback);
+  ~TextureMailbox();
+
+  bool Equals(const TextureMailbox&) const;
+  const int8* Data() const;

[danakj, 2013/01/16 22:22:13]

I'd name this data() and move the body into the header, as it's just an
accessor.

+  bool IsEmpty() const;
+  void RunReleaseCallback(unsigned sync_point) const;
+
+  std::string name_;

[danakj, 2013/01/16 22:22:13]

If these are meant to be public then drop the trailing underscore. That said, is
there a reason to not just add an accessor for them and make them private? This
class isn't for IPC so I think a class pattern would be preferable usually.

+  ReleaseCallback callback_;
+};
+
+}  // namespace cc
+
+#endif  // CC_TEXTURE_MAILBOX_H_