@abhi9u@lemmy.world to Technology@lemmy.worldEnglish • 29 days agoHow Python Compares Floats and Ints: When Equals Isn’t Really Equalblog.codingconfessions.comexternal-linkmessage-square43fedilinkarrow-up1141arrow-down18
arrow-up1133arrow-down1external-linkHow Python Compares Floats and Ints: When Equals Isn’t Really Equalblog.codingconfessions.com@abhi9u@lemmy.world to Technology@lemmy.worldEnglish • 29 days agomessage-square43fedilink
minus-square@MiaoulinkEnglish2•29 days agoThey wouldn’t be running into an issue, but creating one, that’s different
minus-square@Sylvartas@lemmy.worldlinkfedilinkEnglish1•28 days 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@MiaoulinkEnglish3•28 days 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