Ggtcf

What do you call something that goes against the spirit of the law, but is legal when interpreting the law to the letter?

Factorio analysis: data munging

Is Social Media Science Fiction?

Schwarzschild Radius of the Universe

Divisibility of sum of multinomials

Are tax years 2016 & 2017 back taxes deductible for tax year 2018?

Why is "Reports" in sentence down without "The"

Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?

How can the DM most effectively choose 1 out of an odd number of players to be targeted by an attack or effect?

When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?

Distance between two points on a map made for a game

LM317 - Calculate dissipation due voltage drop

Is there a way I can return more than one integer from a method?

Prevent a directory in /tmp from being deleted

Why do we use polarized capacitors?

What Brexit solution does the DUP want?

Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?

Showing the closure of a compact subset need not be compact

Why has Russell's definition of numbers using equivalence classes been finally abandoned? ( If it has actually been abandoned).

What does "enim et" mean?

How can bays and straits be determined in a procedurally generated map?

What is the offset in a seaplane's hull?

N.B. ligature in Latex

Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?

JavaScript type conversion ==

Which equals operator (== vs ===) should be used in JavaScript comparisons?Create GUID / UUID in JavaScript?How do JavaScript closures work?What is the most efficient way to deep clone an object in JavaScript?How do I remove a property from a JavaScript object?Which equals operator (== vs ===) should be used in JavaScript comparisons?How do I include a JavaScript file in another JavaScript file?What does “use strict” do in JavaScript, and what is the reasoning behind it?How to check whether a string contains a substring in JavaScript?How do I remove a particular element from an array in JavaScript?How to use foreach with array in JavaScript?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I recently read a post on reddit that said...

When you start learning JavaScript, you will likely read about never to use == but rather ===.

Which lead me to question:
Is there a time when it’s makes sense to use == rather than ===?

The author replied:

If you need to do type conversion. 420 == "420" evaluates to true.

While I could see how this could be useful if comparing the value of a text input to a number easily the same could be done using toString(). Just curious what other use cases the language designers had in mind? Any good examples of using this language feature properly rather than abusing it or negative behavior?

javascript

share|improve this question

asked Mar 9 at 4:02

Shane RayShane Ray

1,0851617

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Take a look at how lodash uses it in the isNil function (github.com/lodash/lodash/blob/master/isNil.js#L20). They are coercing both null and undefined to falsy. Otherwise they'd need to check both (i.e. value === null || value === undefined)
  
  – lux
  Mar 9 at 4:21
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  You’re right – it’s widely agreed on that it’s a bad idea to ever make use of ==’s type coercion except sometimes in the idiomatic case of == null (which means exactly === null || === undefined). As far as language design, well… lots of parts of JavaScript are mistakes in retrospect.
  
  – Ry-♦
  Mar 9 at 4:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  See stackoverflow.com/questions/359494/…
  
  – R. Schifini
  Mar 9 at 4:52
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Actually strict equality and inequality operators weren't introduced until JavaScript 1.3. They are particularly suited to testing falsey values, e.g. to differentiate between null and undefined. They are not particularly suited to testing if an object value is an object, which is usually tested for using the truthyness of the value without use of comparison operators.
  
  – traktor53
  Mar 9 at 6:06
  
  

  
  
  
  

add a comment | 

0

I recently read a post on reddit that said...

When you start learning JavaScript, you will likely read about never to use == but rather ===.

Which lead me to question:
Is there a time when it’s makes sense to use == rather than ===?

The author replied:

If you need to do type conversion. 420 == "420" evaluates to true.

While I could see how this could be useful if comparing the value of a text input to a number easily the same could be done using toString(). Just curious what other use cases the language designers had in mind? Any good examples of using this language feature properly rather than abusing it or negative behavior?

javascript

share|improve this question

asked Mar 9 at 4:02

Shane RayShane Ray

1,0851617

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Take a look at how lodash uses it in the isNil function (github.com/lodash/lodash/blob/master/isNil.js#L20). They are coercing both null and undefined to falsy. Otherwise they'd need to check both (i.e. value === null || value === undefined)
  
  – lux
  Mar 9 at 4:21
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  You’re right – it’s widely agreed on that it’s a bad idea to ever make use of ==’s type coercion except sometimes in the idiomatic case of == null (which means exactly === null || === undefined). As far as language design, well… lots of parts of JavaScript are mistakes in retrospect.
  
  – Ry-♦
  Mar 9 at 4:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  See stackoverflow.com/questions/359494/…
  
  – R. Schifini
  Mar 9 at 4:52
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Actually strict equality and inequality operators weren't introduced until JavaScript 1.3. They are particularly suited to testing falsey values, e.g. to differentiate between null and undefined. They are not particularly suited to testing if an object value is an object, which is usually tested for using the truthyness of the value without use of comparison operators.
  
  – traktor53
  Mar 9 at 6:06
  
  

  
  
  
  

add a comment | 

I recently read a post on reddit that said...

When you start learning JavaScript, you will likely read about never to use == but rather ===.

Which lead me to question:
Is there a time when it’s makes sense to use == rather than ===?

The author replied:

If you need to do type conversion. 420 == "420" evaluates to true.

While I could see how this could be useful if comparing the value of a text input to a number easily the same could be done using toString(). Just curious what other use cases the language designers had in mind? Any good examples of using this language feature properly rather than abusing it or negative behavior?

javascript

share|improve this question

asked Mar 9 at 4:02

Shane RayShane Ray

1,0851617

share|improve this question

asked Mar 9 at 4:02

Shane RayShane Ray

1,0851617

share|improve this question

asked Mar 9 at 4:02

Shane RayShane Ray

1,0851617

asked Mar 9 at 4:02

Shane RayShane Ray

1,0851617

asked Mar 9 at 4:02

Shane RayShane Ray

1,0851617