<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - calling super() a second time in a constructor should throw"
href="https://bugs.webkit.org/show_bug.cgi?id=151113#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - calling super() a second time in a constructor should throw"
href="https://bugs.webkit.org/show_bug.cgi?id=151113">bug 151113</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=151113#c3">comment #3</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=151113#c2">comment #2</a>)
> > I'm working on patch for this issue.
> > I've created new op code - op_is_empty to check if thisRegister is empty or
> > unassigned before assign value returned from parent constructor(super). I
> > implemented op_is_empty in LLInt and currently working on implementing it in
> > JITOpcodes & DFG
>
> Why do you need a new op code for this? Can't we just use check_tdz?</span >
Doing that would introduce a synthetic try/catch around something we expect
to often be true.</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>