It claims to be 100 times faster than System.Double.IsNaN Yes, that used to be true. You are missing the time-machine to know when this decision was made. Double.IsNaN() didn’t used to look like that. From the SSCLI10 source code: public static bool IsNaN(double d) { // Comparisions of a NaN with another number is always … Read more
Here is a function – (float)randomFloatBetween:(float)smallNumber and:(float)bigNumber { float diff = bigNumber – smallNumber; return (((float) (arc4random() % ((unsigned)RAND_MAX + 1)) / RAND_MAX) * diff) + smallNumber; }
The thing that stands out initially is that your code is highly polymorphic. You should specialize your floating point type uniformly to Double, so GHC (and LLVM) have a chance of applying more aggressive optimizations. Note, for those trying to reproduce, this code imports: import qualified Data.Vector as V import Data.Bits import Data.Time.Clock import System.Random … Read more
The width specifier is the complete width: printf(“%05.1f\n”, myVar); // Total width 5, pad with 0, one digit after . To get your expected format: printf(“% 06.1f\n”, myVar);
You don’t even need to assume IEEE. C89 says in 3.1.2.5: The set of values of the type float is a subset of the set of values of the type double And every other C and C++ standard says equivalent things. As far as I know, NaNs and infinities are “values of the type float“, … Read more
Due to imprecise float comparison you can or your comparison with np.isclose, isclose takes a relative and absolute tolerance param so the following should work: df[‘result’] = df[‘actual_credit’].ge(df[‘min_required_credit’]) | np.isclose(df[‘actual_credit’], df[‘min_required_credit’])
I’d first convert to Decimal and then use Math.Round on the result. This conversion is not strictly necessary, but I always feel a bit uneasy if I round to decimal places while using binary floating points. Math.Round((Decimal)f, 3, MidpointRounding.AwayFromZero) You should also look into the choice of MidpointRounding, since by default this uses Banker’s round, … Read more
In general ++/– is not defined for floats, since it’s not clear with which value the float should be incremented. So, you may have luck on one system where ++ leads to f += 1.0f but there may be situations where this is not valid. Therefore, for floats, you’ll have to provide a specific value. … Read more
In case the negative value is -1.0 or lower, it invokes undefined behavior since the integral part then cannot be represented by an unsigned number. Otherwise, (as in the case of -0.1), if it can be represented by an integer type, it is well-defined behavior. See the C11 standard, ISO 9899:2011: 6.3.1.4 When a finite … Read more
A NaN is returned (under IEEE 754) in order to continue a computation when a truly undefined (intermediate) result has been obtained. An infinity is returned in order to continue a computation after an overflow has occurred. Thus the behaviour Math.sqrt(Double.NEGATIVE_INFINITY); // NaN is specified because it is known (easily and quickly) that an undefined … Read more