@abhi9u@lemmy.world to Technology@lemmy.worldEnglish • 1 year agoHow Python Compares Floats and Ints: When Equals Isn’t Really Equalblog.codingconfessions.comexternal-linkmessage-square43fedilinkarrow-up1143arrow-down19
arrow-up1134arrow-down1external-linkHow Python Compares Floats and Ints: When Equals Isn’t Really Equalblog.codingconfessions.com@abhi9u@lemmy.world to Technology@lemmy.worldEnglish • 1 year agomessage-square43fedilink
minus-square@Miaou@jlai.lulinkfedilinkEnglish2•1 year agoThey wouldn’t be running into an issue, but creating one, that’s different
minus-square@Sylvartas@lemmy.worldlinkfedilinkEnglish1•1 year 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-square@Miaou@jlai.lulinkfedilinkEnglish3•1 year 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