<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Improve binding of JSBuiltinConstructor classes"
href="https://bugs.webkit.org/show_bug.cgi?id=149556#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Improve binding of JSBuiltinConstructor classes"
href="https://bugs.webkit.org/show_bug.cgi?id=149556">bug 149556</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><span class="quote">> It requires bypassing JSDOMGlobalObject wrapper cache, which is another
> efficiency bonus.</span >
My proposal above does not require bypassing the wrapper cache. The singleton wrapper will simply be found in the cache (many times over).
However, of course we can do further optimization to bypass the wrapper cache.
<span class="quote">> We may also want to use a single singleton for all builtin classes.</span >
We may not need an object at all if we are changing things like the wrapper class. I think we should create a JavaScript object that doesn’t wrap a DOM object at all. And I’m not even sure it’s all that challenging to do that. I might take a crack at it.
<span class="quote">> To go further, we may want to skip generation of some needless code (toJS,
> releaseImpl...).
>
> Choice may be guided by the added complexity to the binding generator.
> I plan to take some time on this once the JS builtin architecture is ready
> to implement ReadableStream and WritableStream.</span >
You may be misunderstanding.
My specific proposed change above is entirely local and doesn’t add any complexity to the bindings generator.
Your more ambitious project is different; that will require a change to the bindings generator, but even that probably does not require not a huge one!</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>