JavaScript - Why can I set keys in an Array?

Question

I thought I knew JavaScript pretty decently, until I encountered other developer's code which knocked me down:

var data = [];

As you can see by its name, it's supposed to be used as an associative array (i.e. Object), but it is an Array. And then he assigns values to keys of that array:

data['somekey'] = 'somevalue';

I thought that wasn't possible in JavaScript, I thought it would throw an exception, but it works. Why does it work? Why do we need Objects then, if we can use Arrays instead? Is it considered a bad practice, and should I shame that developer?

Array instances are Objects so you can set properties on them. But the properties you set do not get iterated over by normal means (for of loop, Array.prototype.forEach, etc) unless they are positive integer keys — Patrick Evans
– Patrick Evans, Commented May 16, 2016 at 16:29
Everything is an object in javascript. The same way you can call an index from object using this sintaxe obj['item'] — Marvin Medeiros
– Marvin Medeiros, Commented May 16, 2016 at 16:30

Mike Cluck · Accepted Answer · 2016-05-16 16:27:57Z

5

It works because Arrays are just a special case of Objects. In fact, check this out:

typeof []; // "object"

Arrays give developers additional methods such as push, pop, etc. and allows the internal engines to better optimize them based on the way they are used.

In general, it's better to use a normal object for associative arrays since that's essentially what objects are. There's no real reason to use arrays as "associative arrays" in that case. Likewise, JS engines generally optimize objects into a hashmap-like structure which may or may not happen if you try and use a normal array in the same manner.

answered May 16, 2016 at 16:27

Mike Cluck

32.6k13 gold badges84 silver badges95 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Anthony E · Accepted Answer · 2016-05-16 16:29:19Z

0

Almost all objects in javascript are derived from a hash object in some way or another. It's through this hash that objects like arrays, store their own internal properties and also allow them to be extended and overridden.

For instance, all of the following evaluate to "object":

typeof(null)
typeof([])
typeof({})
typeof(function(){}.prototype)
typeof(new function(){})

answered May 16, 2016 at 16:29

Anthony E

11.3k2 gold badges28 silver badges46 bronze badges

1 Comment

Felix Kling Over a year ago

Well, typeof null only returns "object" because the algorithm says "if the value is null, return 'object'".

Jammy · Accepted Answer · 2016-05-16 16:40:42Z

0

Internally, JavaScript has only objects (and primitive types). Objects are unordered collection of key:value pairs, where key is string and value can be any JavaScript type.

Arrays, though on the outside look like normal arrays of any other language, are actually a special case of objects, with natively supported language syntax.

>typeof []
 "object" 

>Object.prototype.toString.call([]) 
"[object Array]"

answered May 16, 2016 at 16:40

Jammy

712 silver badges14 bronze badges

Comments

BryanGrezeszak · Accepted Answer · 2016-05-16 16:44:37Z

0

Arrays are Objects with some added abilities made specifically to make it easier to use numeric keys in a list-like fashion. So yes, you can assign properties to them like a normal object as well. Those abilities are retained.

As for why you need objects then...because without objects there wouldn't be javascript. Most things in JS are Objects. That's precisely what you're figuring out by noticing you can treat Arrays like Objects. It's a bit backwards to conclude from that that Objects aren't needed when what you're discovering is that they are the base of most things in JS!

answered May 16, 2016 at 16:44

BryanGrezeszak

5772 silver badges8 bronze badges

Comments

David Pine · Accepted Answer · 2016-05-16 17:06:33Z

0

In JavaScript everything is really just key value pairs, take a look @ this -- where I threw together a quick example and hit the Run button towards the upper-right hand corner.

answered May 16, 2016 at 17:06

David Pine

24.6k11 gold badges82 silver badges113 bronze badges

Comments

Bkjain655 · Accepted Answer · 2016-05-16 16:48:33Z

-1

As everybody knows everything in JS are objects which are key : value pairs. Arrays are also objects internally.

var arr = ["this","is","array"];

when define this in JS, Internally it will be defined like an object with key as index.

arr = {0 : "this", 1 : "is", 2 : "array"}.

Also Array is a class which is wrapped over Object class and it has additional methods to access the values.

hope this helps you.

answered May 16, 2016 at 16:48

Bkjain655

2006 bronze badges

3 Comments

Denys Séguret Over a year ago

"everything in JS are objects which are key : value pairs" : no. Some values aren't objects. And no, internally arrays aren't wrapper over objects (not in any of the common JS engines).

Bkjain655 Over a year ago

If we check the prototype chain then the final class from which it will be inherited from will be Object class. Isn't that true. var aa = []; aa.__proto__.__proto__ = Object class?? "Some values aren't objects" -> can you please elaborate little on this?

Denys Séguret Over a year ago

"3" and NaN are JS values but not objects. As for the internals, any JS engine use optimized arrays for dense arrays (and some of them even use typed arrays like arrays of short integers when the optimization is possible).

Collectives™ on Stack Overflow

JavaScript - Why can I set keys in an Array?

6 Answers 6

Comments

1 Comment

Comments

Comments

Comments

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

Comments

1 Comment

Comments

Comments

Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related