We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ordinary_own_property_keys needs a correct implementation.
ordinary_own_property_keys
The main hurdle here is the chronological ordering of steps 3 and 4:
For each own property key P of O that is a String but is not an integer index, in ascending chronological order of property creation, do For each own property key P of O that is a Symbol, in ascending chronological order of property creation, do
Following this, an implementation of the for-in enumeration order defined by EnumerateObjectProperties is required.
for-in
Then, enumerable_own_properties can also be implemented.
enumerable_own_properties
The text was updated successfully, but these errors were encountered:
For-in reform is being discussed in tc39/ecma262#1281, https://github.com/bakkot/for-in-exploration and at the next tc39 meeting: https://docs.google.com/presentation/d/1ppVLFjnd2iGksBXeu97lml2cs9dTRJnJLfufcshvPcs/edit?usp=sharing
Sorry, something went wrong.
This is great news. I won't be at the September meeting but I'll try to learn more at the November's one.
I may dial into the September one to listen in on the discussion.
No branches or pull requests
ordinary_own_property_keys
needs a correct implementation.The main hurdle here is the chronological ordering of steps 3 and 4:
Following this, an implementation of the
for-in
enumeration order defined by EnumerateObjectProperties is required.Then,
enumerable_own_properties
can also be implemented.The text was updated successfully, but these errors were encountered: