NOT FOR LANDING: Hack up CSSParser for speed.

third_party/WebKit/Source/core/css/parser/CSSParserTokenRange.h

Index: third_party/WebKit/Source/core/css/parser/CSSParserTokenRange.h
diff --git a/third_party/WebKit/Source/core/css/parser/CSSParserTokenRange.h b/third_party/WebKit/Source/core/css/parser/CSSParserTokenRange.h
index 707a1ac6a49b1e1e4b0cdb311e529e63c6993289..afb57e71218960f206bd3294ceb74ffc95417804 100644
--- a/third_party/WebKit/Source/core/css/parser/CSSParserTokenRange.h
+++ b/third_party/WebKit/Source/core/css/parser/CSSParserTokenRange.h
@@ -20,9 +20,9 @@ CORE_EXPORT extern const CSSParserToken& staticEOFToken;
 class CORE_EXPORT CSSParserTokenRange {
     DISALLOW_NEW();
 public:
-    CSSParserTokenRange(const Vector<CSSParserToken>& vector)

[esprehn, 2016/04/22 23:30:57]

We could also use a template I suppose to allow inline capacity here. I think
this should probably be explicit though.

[Timothy Loh, 2016/04/27 06:52:05]

IIRC I set it up so that once you have a CSSParserTokenRange you can only create
additional ranges by using makeSubRange. I think this was so that if you
consume() past the end and get the staticEOF token you can still make a range
and it gets the correct last value.

A template is probably fine because you can (I think?) write template<size_t
inlineBuffer> CSSParserTokenRange(const Vector<CSSParserToken, inlineBuffer>&
vector). Maybe it'd be easier to just using CSSParserTokenVector =
Vector<CSSParserToken, 32> and use that everywhere though.

-    : m_first(vector.begin())
-    , m_last(vector.end())
+    CSSParserTokenRange(const CSSParserToken* first, const CSSParserToken* last)
+        : m_first(first)
+        , m_last(last)
     {
     }
 
@@ -71,11 +71,6 @@ public:
     static void initStaticEOFToken();
 
 private:
-    CSSParserTokenRange(const CSSParserToken* first, const CSSParserToken* last)
-    : m_first(first)
-    , m_last(last)
-    { }
-
     const CSSParserToken* m_first;
     const CSSParserToken* m_last;
 };