On 2013/10/31 08:03:20, rossberg wrote:
> > - invoking seal/freeze on an object where not all properties can be
> > sealed/frozen (should still generate a preventExtensions change
record,
IIRC)
>
> I can't think of how to generate this case. How can this arise?
I'm sorry, you are right, it can't -- I keep forgetting that JavaScript
has
this
crank semantics where you can still change a data property from writable
to
non-writable, even if it's allegedly non-configurable. 8/
Hehe... we had the exact same discussion yesterday on IM before we
remembered
the Mark Miller escape hatch.
https://codereview.chromium.org/47703003/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
