make JSProxyHandler::family a data member instead of a virtual method call?

RESOLVED FIXED

Status

()

Core
JavaScript Engine
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: gal, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Might be faster. Only blake will use this, so asking him for input.
Unless mxr is lying to me, JSProxyHandler appears to be gone. Please reopen if that's the case.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
It's now js::ProxyHandler. I don't know if the bug is still valid, though.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: TM: make JSProxyHandler::family a data member instead of a virtual method call? → make JSProxyHandler::family a data member instead of a virtual method call?
This actually got fixed as part of the patch for bug 574299 a long time ago (see jsproxy.h, js::ProxyHandler::family is an inline function and not virtual).
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.