Re: All ECMAScript attributes should be non-configurable

On Sep 23, 2011, at 6:42 PM, David Bruant wrote:

>> No. For "own" the object itself must have a "property map" or equivalent.
> For "inherited", each property must have an internal object-to-value map
> or equivalent.

No, prototype object has that map. You don't need to replicate it in all N=1e6 instances delegating to the prototype. The only thing the instances need (for data properties) are value storage slots.


> Not if the property map is lazily created.

Let's not match implementation c.v.s here. Any lazy approach requires extra state *and* code, to go from lazy to eager. The state, however encoded, must be able to distinguish lazy/unreified from eager/reified. This costs.

/be