<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Vector<Attribute> in HTMLToken, AtomicHTMLToken, and HTMLStackItem should have inline capacity"
href="https://bugs.webkit.org/show_bug.cgi?id=154903#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Vector<Attribute> in HTMLToken, AtomicHTMLToken, and HTMLStackItem should have inline capacity"
href="https://bugs.webkit.org/show_bug.cgi?id=154903">bug 154903</a>
from <span class="vcard"><a class="email" href="mailto:rniwa@webkit.org" title="Ryosuke Niwa <rniwa@webkit.org>"> <span class="fn">Ryosuke Niwa</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=154903#c2">comment #2</a>)
<span class="quote">> Before making this change we should be sure to understand the performance of
> moving a Vector with inline capacity vs. the performance of moving a Vector
> with no inline capacity. We will definitely speed things up by avoiding a
> heap allocation for each Vector when creating it, but we might incur a cost
> when moving the vector between objects.
>
> If we are copying rather than moving, then I suppose it’s guaranteed to be a
> win.</span >
We're always copying these vectors :( I'm all ears if you can think of a way to avoid copying. It's really silly but I haven't quite figured out how to untangle the dependency between lifetimes of these objects yet.</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>