Pass debug name as Vector instead of const char*

src/vector.h

Index: src/vector.h
diff --git a/src/vector.h b/src/vector.h
index e4637c91c9804fe5f191976e0ed1a0f9e7a4979c..d120dfc4ac70c36ff9cbc7340546b356f529babd 100644
--- a/src/vector.h
+++ b/src/vector.h
@@ -24,6 +24,9 @@ class Vector {
     DCHECK(length == 0 || (length > 0 && data != NULL));
   }
 
+  template <int N>
+  explicit Vector(T (&arr)[N]) : start_(arr), length_(N) {}
+
   static Vector<T> New(int length) {
     return Vector<T>(NewArray<T>(length), length);
   }
@@ -201,6 +204,10 @@ inline Vector<char> MutableCStrVector(char* data, int max) {
   return Vector<char>(data, (length < max) ? length : max);
 }
 
+template <typename T, int N>

[titzer, 2016/04/22 11:46:30]

Since this is only ever used for C strings (now), I'd suggest:

inline Vector<const char> CStrVector(const char*[N])

[Clemens Hammacher, 2016/04/22 13:47:54]

CStrVector is already there, but it takes a const char*, and computes the string
length itself; this is unnecessary in many cases.

ArrayVector was meant to be a type-safe generalization of STATIC_CHAR_VECTOR,
and there are indeed 28 places where a pattern like 'Vector<T> vec(buffer,
arraysize(buffer))' is used, where T is char, const char* or HValue*.
Is it desirable to refactor such code, in the belief that ArrayVector is much
nicer?

[titzer, 2016/04/22 13:51:45]

Yeah, I'd rather just make a small addition now and fork off refactoring of the
other places in V8 in another CL. So you can just add a variant of CStrVector if
its possible. I find it reads nicer at call sites to see
CStrVector("somestring") instead of ArrayVector("somestring"): again,
communicating intent.

+inline Vector<T> ArrayVector(T (&arr)[N]) {
+  return Vector<T>(arr);
+}
 
 }  // namespace internal
 }  // namespace v8