<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Fix the incorrectness that AtomicString could have symbolic StringImpl"
href="https://bugs.webkit.org/show_bug.cgi?id=145002#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Fix the incorrectness that AtomicString could have symbolic StringImpl"
href="https://bugs.webkit.org/show_bug.cgi?id=145002">bug 145002</a>
from <span class="vcard"><a class="email" href="mailto:darin@apple.com" title="Darin Adler <darin@apple.com>"> <span class="fn">Darin Adler</span></a>
</span></b>
<pre>Another plus of using RefPtr directly is that it will be more natural to pass types like UniquedStringImpl& and UniquedStringImpl*, rather than const RefPtr<UniquedStringImpl>&, and the former is more efficient. In fact, we would eventually rename UniquedStringImpl to UniquedString, once we figure out what to do about the names of WTF::String and WTF::StringImpl. I think we might at some point name WTF::String something crazy like RefPtrString and give StringImpl the simpler name String.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>