Removing Proxy hasOwn() trap (Was: [[Invoke]] and implicit method calls)
allen at wirfs-brock.com
Wed Sep 25 09:54:00 PDT 2013
On Sep 25, 2013, at 1:26 AM, Tom Van Cutsem wrote:
> I recall that Allen and I had previously agreed that it would be cleanest if each of the [[internal]] methods on Object would correspond 1-to-1 to a trap in the Proxy API (and I believe this is the case for the current ES6 draft).
> So my stance is that we should either remove both hasOwn() and [[HasOwnProperty]], or else remove neither.
Of course, I had assumed that is implicit in the discussion.
> I'm fine either way, but I believe Jason is right that [[HasOwnProperty]] can be refactored as an abstract operation without any perf implications on non-proxy objects.
I think so too. Since there doesn't seem to be any objections I'll tag [[HasOwnProperty]] for the scrap heap.
More information about the es-discuss