[Webkit-unassigned] [Bug 158778] Don't leak the names of [private] functions in JS built-ins

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 22 02:05:39 PDT 2016


--- Comment #3 from Adam Bergkvist <adam.bergkvist at ericsson.com> ---
(In reply to comment #2)
> Let's keep it open for now.
> There may be cases where this issue might arise again.

OK with me.

> Also, usually, the caller of the private method should ensure that
> parameters passed to the function are all fine. In such a case, the checks
> should become assertions.

I haven't looked into the effect of the UNLIKELY macro, but it sounds like something we might want to use it if we still want to keep the "second step argument" checks in native code.

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

More information about the webkit-unassigned mailing list