base: Add/Fix namespace closing comments.

base/threading/thread_restrictions.h

Index: base/threading/thread_restrictions.h
diff --git a/base/threading/thread_restrictions.h b/base/threading/thread_restrictions.h
index 1e5f51080b717e90b59ce95581a93f4284328859..75d89259d3dad8c24f35fe2a6f4dd7d47d7e2b3d 100644
--- a/base/threading/thread_restrictions.h
+++ b/base/threading/thread_restrictions.h
@@ -43,7 +43,7 @@ class NestedMessagePumpAndroid;
 class RenderWidgetResizeHelper;
 class ScopedAllowWaitForAndroidLayoutTests;
 class TextInputClientMac;
-}
+}  // namespace content

[rvargas (doing something else), 2015/03/06 22:53:42]

I'm fine either way, but this is an interesting example for the conversation:

The style guide would require all namespaces to be terminated with a comment
(although even the style guide have at least one example that don't follow that
rule), but the tool clearly considers some things in this file simple enough to
not require the comment...

and given that better readability is the whole point, I'd argue that a few empty
lines in this code will do more for readability than the comment closing the
namespace. Specifically this line reads better without the comment, or with the
comment but an empty line after it, than with comment and no separation from the
next line.

[danakj, 2015/03/06 22:59:18]

Ya this one is weird, I agree. It went over the "obvious where the start of the
namespace" threshold. Personally I am happy to accept something like this to
avoid having to think about it when writing/reviewing CLs though.

Ideally the tool could say "everything inside this namespace is forward
declarations" and ignore it though, IMHO.

 namespace dbus {
 class Bus;
 }