Some nits I found while looking around rAc() code.

chrome/browser/ui/autofill/autofill_dialog_types.h

Index: chrome/browser/ui/autofill/autofill_dialog_types.h
diff --git a/chrome/browser/ui/autofill/autofill_dialog_types.h b/chrome/browser/ui/autofill/autofill_dialog_types.h
index 9c96b8bb97347df4c4482a3ccde74dc1b62e8dd2..be794a0818866b45da2cbe267c104f98c8be4238 100644
--- a/chrome/browser/ui/autofill/autofill_dialog_types.h
+++ b/chrome/browser/ui/autofill/autofill_dialog_types.h
@@ -8,6 +8,10 @@
 #include <map>
 #include <vector>
 
+#ifndef NDEBUG
+#include <ostream>
+#endif
+
 #include "base/callback_forward.h"
 #include "base/strings/string16.h"
 #include "base/time/time.h"
@@ -72,6 +76,10 @@ enum DialogSection {
   SECTION_MAX = SECTION_SHIPPING
 };
 
+#ifndef NDEBUG

[groby-ooo-7-16, 2014/01/04 01:05:45]

All other instances of operator<< that a random sample of the code base turned
up[1] are debug & release. I think we should stick to that pattern, if we MUST
have a ToString.

[1] gfx::Range, GURL, various Quick packet items, etc.

+std::ostream& operator<<(std::ostream& out, DialogSection section);
+#endif
+
 // A notification to show in the autofill dialog. Ranges from information to
 // seriously scary security messages, and will give you the color it should be
 // displayed (if you ask it).