abhi9u@lemmy.world to Technology@lemmy.worldEnglish · 2 years agoHow Python Compares Floats and Ints: When Equals Isn’t Really Equalblog.codingconfessions.comexternal-linkmessage-square43linkfedilinkarrow-up1143arrow-down19
arrow-up1134arrow-down1external-linkHow Python Compares Floats and Ints: When Equals Isn’t Really Equalblog.codingconfessions.comabhi9u@lemmy.world to Technology@lemmy.worldEnglish · 2 years agomessage-square43linkfedilink
minus-squareMiaou@jlai.lulinkfedilinkEnglisharrow-up2·2 years agoThey wouldn’t be running into an issue, but creating one, that’s different
minus-squareSylvartas@lemmy.worldlinkfedilinkEnglisharrow-up1·2 years agoMeh. Imo anyone comparing an integer to a float and not expecting one of them to be implicitly casted to the other’s type will create that issue for themselves when doing the same thing with an explicit cast.
minus-squareMiaou@jlai.lulinkfedilinkEnglisharrow-up3·2 years agoWhat I meant is, the former can be a genuine mistake, the latter is a conscious (probably uneducated) decision
They wouldn’t be running into an issue, but creating one, that’s different
Meh. Imo anyone comparing an integer to a float and not expecting one of them to be implicitly casted to the other’s type will create that issue for themselves when doing the same thing with an explicit cast.
What I meant is, the former can be a genuine mistake, the latter is a conscious (probably uneducated) decision