<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - WebAssembly: test compile / instantiate in a Worker"
href="https://bugs.webkit.org/show_bug.cgi?id=166480#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - WebAssembly: test compile / instantiate in a Worker"
href="https://bugs.webkit.org/show_bug.cgi?id=166480">bug 166480</a>
from <span class="vcard"><a class="email" href="mailto:sbarati@apple.com" title="Saam Barati <sbarati@apple.com>"> <span class="fn">Saam Barati</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=166480#c1">comment #1</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=166480#c0">comment #0</a>)
> > I've heard from someone trying out WebAssembly that they current use compile
> > / instantiate in a worker because some implementations aren't asynchronous.
> > They want to do work on the main thread while compiling, so a Worker makes
> > sense. They then transfer the Module / Instance back to the main thread.
> >
> > We should have a test that this works well.
> >
> > Related:
> > - WebAssembly: Make WebAssembly.compile truly asynchronous
> > <a class="bz_bug_link
bz_status_NEW "
title="NEW - WebAssembly: Make WebAssembly.compile truly asynchronous"
href="show_bug.cgi?id=166016">https://bugs.webkit.org/show_bug.cgi?id=166016</a>
> > - WebAssembly: Implement the WebAssembly.instantiate API
> > <a class="bz_bug_link
bz_status_NEW "
title="NEW - WebAssembly: Implement the WebAssembly.instantiate API"
href="show_bug.cgi?id=165982">https://bugs.webkit.org/show_bug.cgi?id=165982</a>
>
> I think this should work as expected regardless of the compile API being
> asynchronous internally.</span >
Also, I agree we should have a test for this.</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>