<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Cleanup: Make DedicatedWorkerThread::create() an inline template method"
href="https://bugs.webkit.org/show_bug.cgi?id=153612#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Cleanup: Make DedicatedWorkerThread::create() an inline template method"
href="https://bugs.webkit.org/show_bug.cgi?id=153612">bug 153612</a>
from <span class="vcard"><a class="email" href="mailto:aestes@apple.com" title="Andy Estes <aestes@apple.com>"> <span class="fn">Andy Estes</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=153612#c5">comment #5</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=153612#c4">comment #4</a>)
> > It seems somewhat strange to have a one-off variadic template here, since
> > the number of parameters will never actually vary in practice.
> >
> > I wonder if we should consider creating something similar to
> > std::make_unique for Ref and RefPtr? That would let us remove this type of
> > duplication all over our codebase.
>
> I've thought about that. We could even call it static Ref<T> create(...) and
> put it on RefCountedBase!</span >
Yeah, that'd be nice, since it'd let us keep the constructors private.</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>