[Webkit-unassigned] [Bug 74718] Remove the `value' argument to op_push_new_scope

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 19 18:11:09 PST 2011


https://bugs.webkit.org/show_bug.cgi?id=74718





--- Comment #5 from Geoffrey Garen <ggaren at apple.com>  2011-12-19 18:11:09 PST ---
It's not sound to use the same mechanism for block scope as we currently use for catch. Catch is rare, and already slow, so it's OK that catch requires an object allocation and scope chain push/pop. But if "let is the new var", it's not acceptable to allocate a new scope object and push/pop the head of the scope chain every time you enter/exit a let scope. We want a new solution that distinguishes between variables that are captured and variables that aren't, allocates uncultured variables on the stack, and tears of captured variables as needed.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list