c2db077574
Previously, std.debug.assert would `@panic` in test builds, if the assertion failed. Now, it's always `unreachable`. This makes release mode test builds more accurately test the actual code that will be run. However this requires tests to call `std.testing.expect` rather than `std.debug.assert` to make sure output is correct. Here is the explanation of when to use either one, copied from the assert doc comments: Inside a test block, it is best to use the `std.testing` module rather than assert, because assert may not detect a test failure in ReleaseFast and ReleaseSafe mode. Outside of a test block, assert is the correct function to use. closes #1304
41 lines
1.1 KiB
Zig
41 lines
1.1 KiB
Zig
const std = @import("../index.zig");
|
|
const math = std.math;
|
|
const expect = std.testing.expect;
|
|
const maxInt = std.math.maxInt;
|
|
|
|
pub fn isFinite(x: var) bool {
|
|
const T = @typeOf(x);
|
|
switch (T) {
|
|
f16 => {
|
|
const bits = @bitCast(u16, x);
|
|
return bits & 0x7FFF < 0x7C00;
|
|
},
|
|
f32 => {
|
|
const bits = @bitCast(u32, x);
|
|
return bits & 0x7FFFFFFF < 0x7F800000;
|
|
},
|
|
f64 => {
|
|
const bits = @bitCast(u64, x);
|
|
return bits & (maxInt(u64) >> 1) < (0x7FF << 52);
|
|
},
|
|
else => {
|
|
@compileError("isFinite not implemented for " ++ @typeName(T));
|
|
},
|
|
}
|
|
}
|
|
|
|
test "math.isFinite" {
|
|
expect(isFinite(f16(0.0)));
|
|
expect(isFinite(f16(-0.0)));
|
|
expect(isFinite(f32(0.0)));
|
|
expect(isFinite(f32(-0.0)));
|
|
expect(isFinite(f64(0.0)));
|
|
expect(isFinite(f64(-0.0)));
|
|
expect(!isFinite(math.inf(f16)));
|
|
expect(!isFinite(-math.inf(f16)));
|
|
expect(!isFinite(math.inf(f32)));
|
|
expect(!isFinite(-math.inf(f32)));
|
|
expect(!isFinite(math.inf(f64)));
|
|
expect(!isFinite(-math.inf(f64)));
|
|
}
|