Mark S. Miller wrote:
I remember I was for a time in favor of [[SetIntegrity]], and made
arguments in support of it. However, it was additional semantic state
that was approximately redundant with the state already there, and
could get out of sync with it. If now were earlier in the ES6 cycle I
would be open to reconsidering it. But it raised so many open
questions that I don't think we should reopen it unless something is
broken with the current plan. If we do reopen [[SetIntegrity]], we
should decide to slip the schedule.
See, e.g.,
https://mail.mozilla.org/pipermail/es-discuss/2013-February/028854.html
and
https://mail.mozilla.org/pipermail/es-discuss/2013-March/029277.html
We did not have consensus on per-object Get/SetIntegrity. I don't think
we want the redundancy entailed. Implementors I've spoken with do not.
This seems a dead snake, so no need to shoot at it.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
