For std.math.hardware FloatingPointControl, it mentioned uninitialized values of floats.
I.e.
// Enable hardware exceptions for division by zero, overflow to infinity,
// invalid operations, and uninitialized floating-point variables.
https://dlang.org/phobos/std_math_hardware.html#.FloatingPointControl
An uninitialized float can hold a valid value for the type. It may instead by trying to say "default-initialized" instead. However default initialized floats in D are no longer signally NaN's, they are quiet NaN's, so that would not be true either.
For std.math.hardware FloatingPointControl, it mentioned uninitialized values of floats.
I.e.
https://dlang.org/phobos/std_math_hardware.html#.FloatingPointControl
An uninitialized float can hold a valid value for the type. It may instead by trying to say "default-initialized" instead. However default initialized floats in D are no longer signally NaN's, they are quiet NaN's, so that would not be true either.