Skip to content
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

Enumeration order needs to be correctly implemented #28

Open
IgnoredAmbience opened this issue Sep 6, 2018 · 3 comments
Open

Enumeration order needs to be correctly implemented #28

IgnoredAmbience opened this issue Sep 6, 2018 · 3 comments
Labels
feature jsref Tasks impacting jsref design and codebase.

Comments

@IgnoredAmbience
Copy link
Member

IgnoredAmbience commented Sep 6, 2018

ordinary_own_property_keys needs a correct implementation.

The main hurdle here is the chronological ordering of steps 3 and 4:

  1. 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
  2. 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.

Then, enumerable_own_properties can also be implemented.

@IgnoredAmbience IgnoredAmbience added feature jsref Tasks impacting jsref design and codebase. labels Sep 6, 2018
@IgnoredAmbience
Copy link
Member Author

@brabalan
Copy link
Member

This is great news. I won't be at the September meeting but I'll try to learn more at the November's one.

@IgnoredAmbience
Copy link
Member Author

I may dial into the September one to listen in on the discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature jsref Tasks impacting jsref design and codebase.
Projects
None yet
Development

No branches or pull requests

2 participants