Pre-RFC Introduction of Half and Quadruple Precision Floats (f16 and f128)

[scottmcm]

@jjpe

How is something like NonZeroU32 even expressible for resolution at type-check time without something like a dependent type? Would it not need to become something like let x: Result<NonZeroU32, Error> = 1; , to account for the fact that the literal might actually be 0?

Well it's currently proposed that const fns should be allowed to panic!, with the message becoming a compilation error if that path is hit, so one option would be to use that.