@JPDev@programming.dev to Programmer Humor@programming.dev • 5 months ago===programming.devimagemessage-square70fedilinkarrow-up1672
arrow-up1672image===programming.dev@JPDev@programming.dev to Programmer Humor@programming.dev • 5 months agomessage-square70fedilink
minus-squareBougieBirdielinkEnglish6•5 months agoThe other comments explains it in pretty good detail, but when I was learning my teacher explained it sort of like a mnemonic. 1 + 1 = 2 is read “one plus one equals two” 1 + 1 == 2 is read “one plus one is equal to two” 1 + 1 === 2 is read “one plus one is really equal to two” And you hit the nail on the head, is that === is type explicit while == is implicit.
minus-square@bobbykjack@programming.devlinkfedilink3•edit-25 months agoI’d use something like: = becomes == equals === is identical to It’s funny how everyone thinks “equals” in this context should be “identical to” when, in normal language, it doesn’t really mean that at all!
The other comments explains it in pretty good detail, but when I was learning my teacher explained it sort of like a mnemonic.
1 + 1 = 2 is read “one plus one equals two”
1 + 1 == 2 is read “one plus one is equal to two”
1 + 1 === 2 is read “one plus one is really equal to two”
And you hit the nail on the head, is that === is type explicit while == is implicit.
I’d use something like:
= becomes
== equals
=== is identical to
It’s funny how everyone thinks “equals” in this context should be “identical to” when, in normal language, it doesn’t really mean that at all!