How can I check if arrays are equal in javascript?

Question

Have a look at this code sample or go to the jsfiddle

function printRelation(a, b, out) {
    var text;
    if (a === b) {
        text = "a === b";
    } else if (a == b) {
        text = "a == b";
    } else {
        text = "a != b";
    }
    $('#' + out).text(text);
}

var a = [0, 0, 2], b = a;
printRelation(a, b, 'out1');
a = [0, 0, 2];
b = [0, 0, 2];
printRelation(a, b, 'out2');

I would have expected both tests to output a === b, but only the first one does. The second one outputs a != b. Can anyone explain this behaviour? How can I efficiently compare arrays in javascript?

Possible duplicate of http://stackoverflow.com/questions/3115982/how-to-check-javascript-array-equals — JConstantine, Oct 07 '12 at 16:01
I guess the === operator compares arrays by reference, which would explain the observed behaviour. EDIT: Answered by Pointy in the meantime. — Thomas, Oct 07 '12 at 16:01

RKumsher · Answer 1 · 2016-10-18T19:03:59.590

You can use the Underscore.js library's isEqual method.

http://underscorejs.org/#isEqual

Performs an optimized deep comparison between the two objects, to determine if they should be considered equal.

var moe   = {name : 'moe', luckyNumbers : [13, 27, 34]};
var clone = {name : 'moe', luckyNumbers : [13, 27, 34]};
moe == clone;
=> false
_.isEqual(moe, clone);
=> true

UPDATE

Lodash is inspired by underscore, but nowadays is superior solution

https://lodash.com/docs/#isEqual

Performs an optimized deep comparison between the two objects, to determine if they should be considered equal.

var object = { 'a': 1 };
var other = { 'a': 1 };

_.isEqual(object, other);
// => true

object === other;
// => false

note that order matters in an array, so `_.isEqual([1, 2, 3], [3, 2, 1]) => false` — jrz, May 28 '15 at 01:52

Stefan Kendall · Answer 2 · 2015-09-18T22:43:38.863

12

Use lodash.

_.isEqual([1,2],[1,2])

Also works with objects.

_.isEqual({a:1}, {a:1})

edited Sep 18 '15 at 22:43

answered Oct 07 '12 at 16:10

Stefan Kendall

66,414
68
253
406

1

Just wanted to say : this is working great for checking [1, 2] with [1, 2], but not for checking [1, 2] with [2, 1] (lodash check if order is the same). – ersefuril Jul 07 '16 at 07:36

David Hellsing · Answer 3 · 2012-10-07T16:12:29.780

7

Arrays are Objects in javascript. And comparing objects can’t be done using == like you would normally use when comparing strings or numbers.

There are many other ways to compare arrays, my favourite is using JSON:

if ( JSON.stringify(a) == JSON.stringify(b) ) {
    // equal

Note that assigning a pre-existing object to a variable like you do when you write b = a is just copying a reference. They both point to the same array.

You would have to do b = a.slice() to get a real copy.

edited Oct 07 '12 at 16:12

answered Oct 07 '12 at 16:00

David Hellsing

106,495
44
176
212

Nice idea. Works for usual cases but not general purpose. – Prinzhorn Oct 07 '12 at 16:06
Nice solution! +1... It also works with objects, but be careful: var a = {a:0, b:0, c:2}; var b = {c:2, b:0, a:0}; would result "false". – Thomas Oct 07 '12 at 16:07
@Thomas true, they need to have the same "order" to equal so it’s mostly for arrays I guess. – David Hellsing Oct 07 '12 at 16:12
`JSON.stringify`'ing the arrays has other limitations as well since JSON supports only a subset of the value types supported in JavaScript. I personally think it's overkill to create JSON strings, especially considering its serious limitations. – I Hate Lazy Oct 07 '12 at 16:20
@Thomas not necessarily; strictly speaking the behavior is really not well-defined for objects, as JavaScript does not specify the order of property iteration in `for ... in` loops. Of course it can generally be relied upon, but it's a little worrisome to do so from a formal standpoint. – Pointy Oct 07 '12 at 16:24
`var a= [{a:1,b:2}]; var b = [{b:2,a:1}]; JSON.stringify(a) === JSON.stringify(b) -> false`. This answer is wrong. – Stefan Kendall Oct 10 '15 at 16:53

Pointy · Accepted Answer · 2012-10-07T16:26:46.817

2

JavaScript array comparisons like you've written are just simple object reference comparisons. They're not "deep" comparisons element by element.

You can write your own comparison function, something to check that the lengths are the same and the the elements are the same, either in order or not, as fits your needs. edit As others point out, there are several libraries that include array comparison functions. If you find one that meets your definition of "equality" (not unlikely), and you don't mind considering incorporating that library into your architecture, that might be a good idea.

edited Oct 07 '12 at 16:26

answered Oct 07 '12 at 16:00

Pointy

405,095
59
585
614

1

And don't forget to do the reference check first too, in the custom function. – MarioDS Oct 07 '12 at 16:02
@MarioDeSchaepmeester ah yes that's a good idea! No use doing extra work if the two arrays are really the same array! – Pointy Oct 07 '12 at 16:03
2

"Write your own." Christ. No. – Stefan Kendall Oct 07 '12 at 16:09
@StefanKendall: Why would we be afraid of writing a little reusable code that suits our specific needs? – I Hate Lazy Oct 07 '12 at 16:21
@StefanKendall that reflects a limited view of reality there. For all we know, the OP may consider two arrays to be "equal" if they contain the same elements, but not necessarily in the same order. Perhaps they're equal if a string "17" in one array can match a numeric `17` in the other. The point is that the meaning of "equal" is not necessarily always the same. If a library is already in use that contains some generic array equality test, then of course it would be foolish not to use it. – Pointy Oct 07 '12 at 16:21
@user1689607: Because it's not re-usable, you probably didn't write tests or documentation for it, and 3 years from now, I'm going to inherit your project and lose 3 days trying to figure out why my client's site can't make sales. – Stefan Kendall Oct 07 '12 at 19:39
@Pointy: Tests/Code define expected behavior, and there are libraries mentioned which pass the original post's criteria of equal. "Write your own implementation" is a bad gut reaction that leads to code bloat, bugs, and a precedent for duplicating existing functionality. – Stefan Kendall Oct 07 '12 at 19:41
@StefanKendall well an argument could be made that importing Underscore solely to access the array equality comparator would be some "bloat" :-) The assumption that a private implementation would not be re-usable nor be tested is also pretty presumptive. There are good things and bad things about relying on external libraries. The answer has been amended in any case. – Pointy Oct 07 '12 at 19:44
@Pointy: I've run into private implementations of arrayEquals several times. They were all untested and undocumented, and even the ones that were tested required re-learning, versus a library that many people are already familiar with, such as underscore. Underscore is insignificantly small in almost all circumstances. Why is my home-rolled version of async.js worse than async.js? Because nobody has ever used my home-rolled version but me and those on my team. Ergo private implementations suck by default. – Stefan Kendall Oct 07 '12 at 19:47
@StefanKendall I appreciate your clearly explained opinions about this. I do a lot of work in relative isolation, so ideas that challenge my subconscious inclinations are always refreshing. – Pointy Oct 07 '12 at 20:03

How can I check if arrays are equal in javascript?

4 Answers4

UPDATE