-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove [[Enumerate]] and associated reflective capabilities #274
Labels
Comments
@Yongqu print((function()
{
var passed = true;
var proxy = new Proxy({}, {
enumerate: function() {
passed = false;
}
});
for(var key in proxy); // Should not throw, nor execute the 'enumerate' method.
return passed;
})()); Expected: true |
Removing 1.2 milestone due to backward compatibility concern. Please fix this in Master. |
leirocks
added a commit
to leirocks/ChakraCore
that referenced
this issue
May 12, 2016
leirocks
added a commit
to leirocks/ChakraCore
that referenced
this issue
May 16, 2016
leirocks
added a commit
to leirocks/ChakraCore
that referenced
this issue
Jun 6, 2016
leirocks
added a commit
to leirocks/ChakraCore
that referenced
this issue
Aug 25, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the January TC39 meeting and subsequent conversations we got consensus on removal of the [[Enumerate]] MOP operation and the associated Reflect.enumerate and proxy trap
enumerate
. A PR implementing this consensus is here: tc39/ecma262#367.The text was updated successfully, but these errors were encountered: