float init 0 request

[Guillaume Piolat]

On Monday, 17 August 2026 at 07:47:09 UTC, pete wrote:
> There is something I don't understand here. If an uninitialised 
> float is an error then why does the compiler not just raise it 
> at compile time rather than setting it to a value that is 
> always wrong and letting someone *hopefully* find it at runtime?
>

Change NaN with null and you'll see how that argument doesn't 
stand. Why would the compiler compile a pointer initialized to 
null?