Comment on Java

maniacal_gaff@lemmy.world ⁨1⁩ ⁨year⁩ ago

• larvyde@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  int coerces to double automatically, without explicit casting

  source

  • snake_baitman@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

    The CPU has to do real work to convert between float and int types. Returning an int type would just be giving the CPU extra work to do for no reason

    source

    • notnotmike@programming.dev ⁨1⁩ ⁨year⁩ ago

      I’m learning so much from this thread and I don’t even use Java

      source
• baseless_discourse@mander.xyz ⁨1⁩ ⁨year⁩ ago

  I think one of the main reason to use floor/ceilling is to predictably cast a double into int. This type signature kind of defeats this important purpose.

  I don’t know this historical context of java, but possibly at that time, people see type more of a burden than a way to garentee correctness? (which is kind of still the case for many programmers, unfortunately.

  source

  • BorgDrone@lemmy.one ⁨1⁩ ⁨year⁩ ago

    You wouldn’t need floor/ceil for that. Casting a double to an int is already predictable as the java language spec explicitly says how to do it, so any JVM will do this the exact same way.

    The floor/ceil functions are simply primitive math operations and they are meant to be used when doing floating point math.

    source

    • baseless_discourse@mander.xyz ⁨1⁩ ⁨year⁩ ago

      “predicable” in the sense that people know how it works regardless what language they know.

      I guess I mean “no surprise for the reader”, which is more “readability” than “predictability”

      source

      • BorgDrone@lemmy.one ⁨1⁩ ⁨year⁩ ago

        Is there any language that doesn’t just truncate when casting from a float to an int?

        source

        • -> View More Comments