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

Map and Set iterator methods should iterate only over own properties #65

Open
medikoo opened this issue Apr 6, 2016 · 0 comments
Open
Assignees

Comments

@medikoo
Copy link
Owner

medikoo commented Apr 6, 2016

Currently implemented idea is that forEach, some etc. iterate also over properties that come from prototypes (e.g. to also provide getter values). Still it proved to be very problematic for implementation internals and it's also not on par with how language iterators work, therefore confusing.

The case of nested and multiple should work same. So if object has non of them resolved to the moment, it should be saturated with those before iteration. For that we may provide also saturate method that's invoked upfront, or even better, a method that will return list of all keys that should be iterated (then iterated keys will be resolved on the go, it's more optimal approach when some or every is concerned)

@medikoo medikoo self-assigned this May 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant