Movement against float.init being nan

[claptrap]

On Sunday, 21 August 2022 at 16:51:51 UTC, Walter Bright wrote:
> Consider the following pattern, which doesn't appear
>
>
> 1. x is default initialized to NaN. bar(x) produces a NaN 
> result on everything dependent on x. User knows there's a 
> problem.
>
> 2. x is default initialized to 0. bar(0) may exhibit problems, 
> but these problems won't necessarily be noticed.

This is the problem, you suggest that if a variable is zero 
initialised in error the problems it causes "wont necessarily" be 
noticed.

I'm saying that's not true, I'm saying it will almost always be 
noticed.