• Killing_Spark@feddit.de
        link
        fedilink
        arrow-up
        19
        ·
        1 year ago

        Only to 2^54. The amount of integers representable by a long is more. But it can and does represent every int value correctly

        • parlaptie@feddit.de
          link
          fedilink
          arrow-up
          5
          arrow-down
          6
          ·
          1 year ago

          *long long, if we’re gonna be taking about C types. A long is commonly limited to 32 bits.

          • Aux@lemmy.world
            link
            fedilink
            arrow-up
            15
            ·
            1 year ago

            C is irrelevant because this post is about Java and in Java long is 64 bits.

          • voxel@sopuli.xyz
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            1 year ago

            you should never be using these types in c anyway, (u?)int(8/16/32/64)_t are way more sane

    • fsxylo@sh.itjust.works
      link
      fedilink
      arrow-up
      27
      ·
      1 year ago

      Also because if you are dealing with a double, then you’re probably dealing with multiple, or doing math that may produce a double. So returning a double just saves some effort.

    • pomodoro_longbreak@sh.itjust.works
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      Yeah it makes sense to me. You can always cast it if you want an int that bad. Hell just wrap the whole function with your own if it means that much to you

      (Not you, but like a hypothetical person)

      • RoyaltyInTraining@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        A double can represent numbers up to ± 1.79769313486231570x10^308, or roughly 18 with 307 zeroes behind it. You can’t fit that into a long, or even 128 bits. Even though rounding huge doubles is pointless, since only the first dozen digits or so are saved, using any kind of Integer would lead to inconsistencies, and thus potentially bugs.

    • karlthemailman@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      How does that work? Is it just because double uses more bits? I’d imagine for the same number of bits, you can store more ints than doubles (assuming you want the ints to be exact values).

        • karlthemailman@sh.itjust.works
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          1 year ago

          No, I get that. I’m sure the programming language design people know what they are doing. I just can’t grasp how a double (which has to use at least 1 bit to represent whether or not there is a fractional component) can possibly store more exact integer vales than an integer type of the same length (same number of bits).

          It just seems to violate some law of information theory to my novice mind.

          • whats_a_refoogee@sh.itjust.works
            link
            fedilink
            arrow-up
            8
            ·
            1 year ago

            It doesn’t. A double is a 64 bit value while an integer is 32 bit. A long is a 64 bit signed integer which stores more exact integer numbers than a double.

            • LeFantome@programming.dev
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              1 year ago

              Technically, a double stores most integers exactly ( up until a certain value ) and then approximations of integers of much larger sizes. A long stores all its integers exactly but cannot handle values nearly as large.

              For most real world data ranges, they are both going to store integers exactly.

          • unawareallium@sh.itjust.works
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            You can think of a double as having a fixed precision, but, in contrast to an integer, this precision can be moved over the decimal point depending on the value you want to represent. Therefore, despite representing floating-point numbers, a double still has discrete steps determined by its binary representation of 64 bits. If the value of a double gets larger, it reaches a point where the smallest difference between two subsequent doubles is greater than one. For float (32 bit), you reach this point at 16777216. The next larger number to be represented as a float is 16777218 (i.e., +2).

            Here is a nice online tool that demonstrates this (and contains much more information on the encoding of floating-point numbers): https://www.h-schmidt.net/FloatConverter/IEEE754.html

            • karlthemailman@sh.itjust.works
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              I agree with all that. But I’m talking about exact integer values as mentioned in the parent.

              I just think this has to be true: count(exact integers that can be represented by a N bit floating point variable) < count(exact integers that can be represented by an N bit int type variable)

            • karlthemailman@sh.itjust.works
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              1 year ago

              I don’t think that’s possible. Representing more exact ints means representing larger ints and vice versa. I’m ignoring signed vs. unsigned here as in theory both the double and int/long can be signed or unsigned.

              Edit: ok, I take this back. I guess you can represent larger values as long as you are ok that they will be estimates. Ie, double of N (for some very large N) will equal double of N + 1.

          • nile@sopuli.xyz
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            Oh now I get what you mean, and like others mentioned, yeah it’s more bits :)

          • Akagigahara@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            I would need to look into the exact difference of double vs integer to know, but a partially educated guess is that they are referring to Int32 vs double and not Int64, aka long. I did a small search and saw that double uses 32 bits for the whole numbers and the others for the decimal.

            • karlthemailman@sh.itjust.works
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              Yeah, that was my guess too. But that just means they could return a long (or whatever the 64 bit int equivalent in java is) instead of an int.

              • Akagigahara@lemmy.world
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                Okay, so I dug in a bit deeper. Doubles are standardized as a 64 bit bundle that is divided into 1 signed bit, 11 exponetioal bits and 52 bits for decimal. It’s quite interesting. As to how it works indepth, I probably will try to analyze a bit conversion if I can try something

          • towerful@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            I’m going to guess here (cause I feel this community is for learning)…
            Integers have exactness. Doubles have range.
            So if MAX_INT + 1 is possible, then ~(MAX_INT + 1) is probably preferable to an overflow or silent MIN_INT.

            But Math.ceil probably expects a float, because it is dealing with decimals (or similar). If it was an int, rounding wouldn’t be required.
            So if Math.ceil returned and integer, then it could parse a float larger than INT_MAX, which would overflow an int (so error, or overflow). Or just return a float