Mojo: Drive-by include fixes.

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

 // Copyright 2014 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 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"
 
 namespace mojo {
 
 template <typename E>
 inline size_t GetSerializedSize_(const Array<E>& input);
 
 template <typename E, typename F>
@@ skipping 151 matching lines @@
   if (input) {
     internal::ArraySerializer<E, F>::DeserializeElements(input, output);
   } else {
     output->reset();
   }
 }
 
 }  // namespace mojo
 
 #endif  // MOJO_PUBLIC_CPP_BINDINGS_LIB_ARRAY_SERIALIZATION_H_