• Womble@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 month ago

    But how far should that be taken should 8 == 8 return false because one is an unsigned int and the other is signed? Or 0.0 == 0.0 where they are floats and doubles? You can make a case for those due to a strong type system but it would go against most peoples idea of what equality is.

    • muntedcrocodile@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      If bits aren’t same then i dont want it to tell me they are the same. And python just has one implementation for int and float.

      I like python cos everything’s an object i dont want different types of objects to evaluate the same they are fundamentally different objects is that not what u would expect?

      • Womble@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month ago

        Even in python you can have control of what types of numbers are used under the hood with numpy arrays (and chances are if you are using floats in any quantity you want to be using numpy). I would be very surprised if array([1,2,3], dtype=uint8) == array([1,2,3], dtype=int16) gave [False, False, False]. In general I think == for numbers should give mathematical equivalence, with the understanding that comparing floats is highly likely to give false negatives unless you are extremely careful with what you are comparing.