Mojo: Drive-by include fixes.

mojo/public/cpp/bindings/lib/array_serialization.h

Index: mojo/public/cpp/bindings/lib/array_serialization.h
diff --git a/mojo/public/cpp/bindings/lib/array_serialization.h b/mojo/public/cpp/bindings/lib/array_serialization.h
index 83403d5250218e91799b7c5b7f09b7fc49e0d051..0c4aea246205bf2d7e4569486d1317f511818538 100644
--- a/mojo/public/cpp/bindings/lib/array_serialization.h
+++ b/mojo/public/cpp/bindings/lib/array_serialization.h
@@ -5,7 +5,9 @@
 #ifndef MOJO_PUBLIC_CPP_BINDINGS_LIB_ARRAY_SERIALIZATION_H_
 #define MOJO_PUBLIC_CPP_BINDINGS_LIB_ARRAY_SERIALIZATION_H_
 
-#include <string>
+#include <string.h>  // For |memcpy()|.

[yzshen1, 2014/07/18 20:52:49]

nit, optional: I think it is no need to explain why we need an include. It gets
out of sync easily (e.g., someone adds a call to another function in string.h).

[viettrungluu, 2014/07/18 20:59:33]

Generally, I agree with you, but since the requirement for string.h isn't quite
so obvious, it makes it very easy to accidentally remove this include (since in
reality string.h always gets included from somewhere).

(Presumably, if someone calls something else in string.h, they'd first check
that string.h is included, and notice that it is and remove/update the comment.
Admittedly, "ideally" is probably more true than "presumably"....)

[yzshen1, 2014/07/18 21:01:26]

Okay. I don't have a string opinion on this one.

+
+#include <vector>
 
 #include "mojo/public/cpp/bindings/lib/array_internal.h"
 #include "mojo/public/cpp/bindings/lib/string_serialization.h"