<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Strict Equality on objects should only check that one of the two sides is an object."
href="https://bugs.webkit.org/show_bug.cgi?id=145992#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Strict Equality on objects should only check that one of the two sides is an object."
href="https://bugs.webkit.org/show_bug.cgi?id=145992">bug 145992</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>Comment on <span class=""><a href="attachment.cgi?id=254990&action=diff" name="attach_254990" title="Patch Expected File">attachment 254990</a> <a href="attachment.cgi?id=254990&action=edit" title="Patch Expected File">[details]</a></span>
Patch Expected File
I’m probably not qualified to review the patch. But was just wondering: Would it be faster to do an early exit if the two values are identical before doing any type checking? Then if the type is object we can return false. It seems that this makes strict equality comparisons of objects that turn out to be equal faster without slowing down the ones that turn out to be not equal. But maybe it would slow down some other important cases? Besides objects, I believe that undefined, null, booleans, and integers would all benefit from this. Floating point numbers and strings might be slowed down slightly by the extra check, I guess.</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>