3 ms·
I think this is the correct way to handle this. I don’t know how many times I’ve been stymied by integer arithmetic and precision loss by implicit conversion. H
by redwoolf 2y ago
I think this is the correct way to handle this. I don’t know how many times I’ve been stymied by integer arithmetic and precision loss by implicit conversion. How should this be handled? Should the int be converted to a double before the operation, should the double be converted to int before the operation, or should the result be converted to an int or a double? As someone who writes code in many languages in a day, these implicit conversion rules can be difficult to remember. It’s best to enforce the developer to be explicit about the intention.
- Dylan16807 2y ago> Should the int be converted to a double before the operation, should the double be converted to int before the operation, or should the result be converted to an int or a double? Isn't it pretty evident that implicit conversions should only go from integer to floating point? > precision loss by implicit conversion That's a reasonable worry, but "Int" in general is only safe to store 32 bits, and 32 bit integers will losslessly convert to doubles.