float init 0 request

[monkyyy]

On Saturday, 15 August 2026 at 22:48:11 UTC, Walter Bright wrote:
> As for the graphics case, what happened is the error showed 
> itself immediately, which is much better than having a subtle 
> unintended 0 initialization that may go undetected for years.

The intended initialization is 0 the vast majority of the time

> There's no getting away from dealing with NaNs. Default 
> initialization to zero is not going to make that go away. The 
> std.math functions are all carefully crafted to correctly deal 
> with NaNs.

false 0's are not unnoticeable they render at the origin or as 
pure black and I generally need to rewrite all math functions to 
*not* be nan friendly because nan propagating is a problem.

Your just asserting terrible takes for video games, cause they 
aint airplane surgery. Failures that do something are amusing; 
doing nothing is very bad and all the c libs treat nan as a 
rareish value cause in c their data structures 0 initialize.

There more a video game community then dlang airplane surgery 
companies.