Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why {} == {} is false, but {} + {} == {} + {} is true

Tags:

Why in node.js is {} == {} equivalent to false, but is {} + {} == {} + {} equivalent to true?

> {} == {} false 
> {} + {} == {} + {} true 
like image 711
0xAX Avatar asked Jul 21 '13 17:07

0xAX


People also ask

Why {} === {} is false in JavaScript?

Each object, each {} is distinct. Same applies to arrays, too. Show activity on this post. 2) it does not make any difference whether you use == or === for comparing objects, because comparing them always returns false.

Why is [] == [] False?

The reason for [] == false even though [] is truthy is: the comparison [] == false compares the value of [] to false . And to get the value of [] , the JavaScript engine first calls [].

Why True == true is false in JavaScript?

If the two operands are not of the same type, JavaScript converts the operands then applies strict comparison. If either operand is a number or a boolean, the operands are converted to numbers if possible; else if either operand is a string, the other operand is converted to a string if possible.

Why ![] Is false?

![] evaluates to false because the reference is truthy. [] can be converted to a number ( 0 in this case ) which is a falsy value. Therefore: the condition passes as equal.


1 Answers

+ here is the string-concatenation operator. This:

{} == {} 

means "if I create one object with {}, and another object with {}, are they the same object?"; and the answer is "no".

This:

{} + {} == {} + {} 

means "is the primitive string "[object Object][object Object]" the same as the primitive string "[object Object][object Object]"?"; and the answer is "yes".


Edited to add: A number of commenters point out that in Chrome's Web Console, {} + {} performs numeric addition, NaN + NaN, such that {} + {} == {} + {} actually returns false (because it's not true that NaN == NaN). Firefox's Web Console gives the same result as Chrome's, but if you run this inside a page, it gives the same result as node.js.

[Redacted: long explanation of how the spec dictates that {} + {} should be string concatenation and {} + {} == {} + {} should be true; the explanation, while correct, is no longer terribly interesting, given the below.]


Edited to add: Thanks to a comment by jJ', I can now offer a better explanation of the inconsistency.

The reason for the Web Console's behavior is that the Web Console does not specifically require an expression; it will happily accept something like if(true) { }. So, when it sees {} + {}, it doesn't interpret that as an expression; the initial {} is interpreted as a naked block, then the + {} is interpreted as an expression (creating a new object, converting it to a primitive number — namely NaN — and evaluating to that number). The Web Console displays the result of the last expression (e.g., the input 3; 4 will give the output 4), which in this case is NaN.

{} + {} == {} + {}, similarly, is interpreted as "empty block, followed by (+{}) == ({} + {})", i.e., "empty block, followed by NaN == '[object Object][object Object]'", i.e. "empty block, followed by false".

This can be fixed by using parentheses; ({} + {} == {} + {}), for example, returns true.

(This behavior, by the way, is not completely specific to the Web Console. eval follows the same rules, such that eval('{} + {}') is NaN and eval('({} + {})') is'[object Object][object Object]'.)

like image 108
ruakh Avatar answered Oct 02 '22 13:10

ruakh