Object.seal, read references, and code reliability
tj.crowder at farsightsoftware.com
Mon Aug 14 18:24:07 UTC 2017
On Mon, Aug 14, 2017 at 7:16 PM, Alex Kodat <akodat at rocketsoftware.com>
> FWIW, I’m not sure I agree with your OrdinaryGet steps.
Why not? (Not that spec language is important at this stage.)
> Also, not sure I like readExtensible as it doesn’t really have
> anything to do with extensibility.
That's fine, it was just a placeholder variable name in an internal method.
:-) `"sealed"` and `"frozen"` are referred to with that terminology, and
this is in the same general area although it isn't literally extensibility.
> In any case, I think the description of [[Get]] would have to be
Why do you think `[[Get]]` needs a flag? The object will have the flag on
it, and `[[Get]]` has the object.
`OrdinaryGet` certainly doesn't need the flag. It has the object, and it
has the relevant object at each stage in the prototype chain (note that
it's indirectly recursive via `[[Get]]`).
Again, though, spec language isn't important at this stage. It's a good
idea and I'd love to see it get legs.
-- T.J. Crowder
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss