ToPropertyDescriptor, [[HasProperty]], & [[HasOwnProperty]]

Andrea Giammarchi andrea.giammarchi at gmail.com
Thu May 8 14:41:54 PDT 2014


OK, hasOwnProperty per descriptor would work too ... probably even easier
as spec change than having all null objects

+1 to that


On Thu, May 8, 2014 at 2:35 PM, John-David Dalton <
john.david.dalton at gmail.com> wrote:

> > I agree with you that this would be a much better design, but it would
> break backwards compatibility with ES5, no?
>
> There have been other changes to the spec that are technically back-compat
> breaking like Object.keys('x') no longer throwing an error.
> I think this change would benefit developers as the case seems to be devs
> getting bitten by the current behavior.
>
> > Minor nitpick: I guess you mean to say that ToPropertyDescriptor should
> use the abstract operation HasOwnProperty, not [[HasOwnProperty]]
>
> Sure, I'll switch to ES6y terms. Yes, I mean the abstract operation
> HasOwnProperty.
>
> - JDD
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140508/aaa9b6c7/attachment.html>


More information about the es-discuss mailing list