Scoped binding of a method to an object
brendan at mozilla.com
Sun Oct 13 10:49:28 PDT 2013
> Erik Arvidsson <mailto:erik.arvidsson at gmail.com>
> October 13, 2013 10:32 AM
> We did proposes this back in 2011
> I wasn't at this actual F2F meeting so I don't know many details.
> Brendan might remember what the blocking issue was?
I wrote why in my reply, cited below:
> Your subject recalls a defunct proposal to add lexically-scoped but
> heap-based -- therefore object property-lookup performance hindering
> -- extension properties. This proposal died precise because of the
> performance problem.
Every property access sprouts a third parameter beyond object and
property name, namely a lexical scope token of some kind. All property
maps in objects shared in the heap also sprout such a scope token along
with property name.
(This is quite reminiscent of ES4 namespaces, which we agreed to reject
from any future ECMA-262 in order to forge Harmony in 2008. See
Implementors objected, including V8 folks (if I recall correctly,
Andreas Rossberg). This was at the May 2011 TC39 meeting hosted at the
University of California at Santa Cruz.
More information about the es-discuss