<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [JSC] implement async functions proposal"
href="https://bugs.webkit.org/show_bug.cgi?id=156147#c44">Comment # 44</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [JSC] implement async functions proposal"
href="https://bugs.webkit.org/show_bug.cgi?id=156147">bug 156147</a>
from <span class="vcard"><a class="email" href="mailto:caitp@igalia.com" title="Caitlin Potter (:caitp) <caitp@igalia.com>"> <span class="fn">Caitlin Potter (:caitp)</span></a>
</span></b>
<pre>JSC::Options is initialized during JSC::initializeThreading(), and the flag state is stored statically --- RuntimeFlags is currently closely associated with JSGlobalObject, and the flags can be stored in a port-independent manner, retrieved via a method virtual method.
For the Parser to get at these flags, something else holding the flag needs to be accessible --- even when a JSGlobalObject isn't (which is the case when Functions need to be reparsed, for example).
Having lots of different copies of these runtime flags seems problematic in case they get out of sync somehow, so it's not necessarily the right way to go about setting these.</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>