[Webkit-unassigned] [Bug 170927] New: How we decide to emit a check for .call and .apply seems slightly wrong

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 17 18:22:59 PDT 2017


            Bug ID: 170927
           Summary: How we decide to emit a check for .call and .apply
                    seems slightly wrong
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sbarati at apple.com
                CC: benjamin at webkit.org, fpizlo at apple.com,
                    ggaren at apple.com, gskachkov at gmail.com,
                    jfbastien at apple.com, keith_miller at apple.com,
                    mark.lam at apple.com, msaboff at apple.com,
                    ticaiolima at gmail.com, utatane.tea at gmail.com

Currently, we just test if we're in a builtin. However, it's conceivable a builtin really wants to grab the public ".call" or ".apply".
Instead, we should probably check if "call" or "apply" is the private symbol, and if so, set a bit in the various AST nodes when we create them.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170418/d150efd5/attachment.html>

More information about the webkit-unassigned mailing list