Clean up on byte_stream (mainly style and includes)

content/browser/byte_stream.h

Index: content/browser/byte_stream.h
diff --git a/content/browser/byte_stream.h b/content/browser/byte_stream.h
index b16664f3142a3f67197131e8d9c23ff0a0584363..7146e7942a6e16c0423423d8deba1106d4ad23ae 100644
--- a/content/browser/byte_stream.h
+++ b/content/browser/byte_stream.h
@@ -5,19 +5,15 @@
 #ifndef CONTENT_BROWSER_BYTE_STREAM_H_
 #define CONTENT_BROWSER_BYTE_STREAM_H_
 
-#include <deque>
-#include <set>
-#include <utility>
-
 #include "base/callback.h"
 #include "base/memory/ref_counted.h"
-#include "base/synchronization/lock.h"
+#include "base/memory/scoped_ptr.h"
 #include "content/common/content_export.h"
 #include "net/base/io_buffer.h"
 
 namespace base {
 class SequencedTaskRunner;
-}
+}  // namespace base

[Randy Smith (Not in Mondays), 2013/08/02 18:43:05]

Can you give me a pointer to the section of the style guide that specifies this
behavior?  I agree that it's common practice (including in the style guide
examples) to include a "// namespace" at the end of the namespace, but I can't
find it specified, and in that context, putting a closing comment two lines
after the namespace opening seems like unnecessary distracting text--it's
obvious to anyone looking at this code what the closing brace refers to.  (I
don't feel strongly, but I do have an opinion, so I'd like to at least have a
specific style guide directive to weigh against that opinion.)

[tyoshino (SeeGerritForStatus), 2013/08/05 07:53:11]

Yes, it's not explicitly stated but a common practice.
OK. It makes sense. Removed.

 
 namespace content {