<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION: Reproducible crash in operatorString() on invalid code with async"
href="https://bugs.webkit.org/show_bug.cgi?id=165091#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION: Reproducible crash in operatorString() on invalid code with async"
href="https://bugs.webkit.org/show_bug.cgi?id=165091">bug 165091</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>The token flags right now are something like this:
R = right-associative bit
T = unterminated error flag
E = error flag
I = binary operator allows 'in'
P = binary operator precedence
K = keyword flag
U = unary operator flag
0b000000000RTEIIIIIIIIPPPPKUXXXXXX
Since the bitfield is 32bits to begin with, do we lose much by allowing 127 keyword / unary op tokens?</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>