Why javascript committee decided to introduce Object.entries instead of Object.prototype.entries?

Asked Jul 30 '17 at 14:56

Active Jul 30 '17 at 14:56

Viewed 33 times

I would highly appreciate if someone could enlighten me why javascript committee has chosen Object.entries, Object.keys, Object.values, over Object.prototype.entries. Object.prototype.keys, Object.prototype.values.

I am asking this question because it's for me unclear what was the motivation for choosing one implementation over another. For instance why an Array got those functions bind to a prototype whereas Object does not. I've tried to search through committee specs, but it did not found an answer.

asked Jul 30 '17 at 14:56

FieryCod

1,674
1
19
27

Because an object should not be concerned with obtaining its own entries and other reflective API. This is about design. Going to find the source. – Benjamin Gruenbaum Jul 30 '17 at 15:04
1

What if the object has it's own `entries` property which overwrites the old `entries`? You'd have to use `Object.prototype.entries.call(obj)`. Quite ugly. – PeterMader Jul 30 '17 at 15:05
@BenjaminGruenbaum https://stackoverflow.com/a/9746215/1048572? – Bergi Jul 30 '17 at 15:09
@Bergi yes! thanks for digging the source! – Benjamin Gruenbaum Jul 30 '17 at 15:12
@Bergi that and https://esdiscuss.org/topic/es3-1-object-static-methods-rationale-document discussing other rationale for sandboxing. – Benjamin Gruenbaum Jul 30 '17 at 15:12

Why javascript committee decided to introduce Object.entries instead of Object.prototype.entries?

0 Answers0

Linked