Looking at the coverage reports there are some private methods in BigFraction that validate input arguments that cannot be incorrect since only BigFraction is calling these methods, i.e. the validations are redundant.
I propose to drop the validation of the exponent length and significandLength in toFloatingPointBits(…) and the validation of the number of bits in the method that it calls (roundAndRightShift). An alternative is to replace with assert statements that will be removed in non-debug code. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
