Is there any way to determine the maximum and minimum floats that can be stuffed into @floatToInt() without invoking safety-checked undefined behaviour? The float/int combinations are known at compile time - currently f32/int32 & f64/int64.
(I'm currently improving my Zig skills by converting some files in the Lua C source to Zig. The Lua code is good quality with tests - nice to work with.)