Function identity of non-configurable accessors

Brendan Eich brendan at
Sat Dec 15 10:11:06 PST 2012

David Bruant wrote:
>> If I create a non-configurable property with a getter that I define 
>> (such
>> as `() => 3`), I know that accessing the property will always produce
>> a known value.    Relaxing this restriction means that proxies could
>> produce whatever they wanted in this situation.
> Indeed. Note that it's true currently true with ES5 host objects.
> The frozen getter/setter could be a working solution as well. 

Frozen accessors would be best if we can get away with the 
incompatibility. Another proposal for public-script-coord or better.


More information about the es-discuss mailing list