Movement against float.init being nan

[apz28]

On Friday, 26 August 2022 at 01:01:24 UTC, Walter Bright wrote:
> On 8/25/2022 10:38 AM, Steven Schveighoffer wrote:
>> 0 is no better here *but also no worse*.
>
> 0 is equal or worse than NaN. It is true that sometimes 0 is 
> equal. But it is *never* better.
>
>
> Using 0x00 was nowhere near as effective.

This seem be another string auto-decode problem to a basic type. 
It should implement similar to CheckedInt (as CheckedFloat?) for 
each case usage; not shoe horn into all use-cases