Add toStdString methods to CString and WTF::String

third_party/WebKit/Source/wtf/text/WTFString.h

Index: third_party/WebKit/Source/wtf/text/WTFString.h
diff --git a/third_party/WebKit/Source/wtf/text/WTFString.h b/third_party/WebKit/Source/wtf/text/WTFString.h
index 256abc6a131a9904461570997cf74da03650d099..e57c17f9e5d353476abf65a7dc8853ea65dcd67c 100644
--- a/third_party/WebKit/Source/wtf/text/WTFString.h
+++ b/third_party/WebKit/Source/wtf/text/WTFString.h
@@ -33,6 +33,7 @@
 #include "wtf/text/StringView.h"
 #include <algorithm>
 #include <iosfwd>
+#include <string>
 
 #ifdef __OBJC__
 #include <objc/objc.h>
@@ -179,6 +180,8 @@ public:
     CString latin1() const;
     CString utf8(UTF8ConversionMode = LenientUTF8Conversion) const;
 
+    std::string toUTF8() const;

[esprehn, 2015/09/30 18:15:39]

This is confusing with the .utf8() method. I'm also hesitant to do this yet, we
shouldn't be using std::string in almost all blink code.

[tkent, 2015/10/01 02:09:06]

At least, the function should have a document that we should use it only to pass
stings to Chromium.

[Primiano Tucci (use gerrit), 2015/10/01 07:34:51]

So, what is the final take? keep it and document? Or rely on
utf8().toStdString() ?
I think we need to come up with a decision here.
Is there the possibility that in future WTFString.toStdString() could do
something smarter (read: more efficient) than utf8().toStdString() ?
If so I think we should go for keeping here and documenting as tkent suggested.

+
     UChar operator[](unsigned index) const
     {
         if (!m_impl || index >= m_impl->length())