Closed Bug 566959 Opened 14 years ago Closed 13 years ago

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

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: gal, Unassigned)

Details

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
Closed: 13 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
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.