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
40 lines
1.2 KiB
Zig
40 lines
1.2 KiB
Zig
const __fixunsdfsi = @import("fixunsdfsi.zig").__fixunsdfsi;
|
|
const testing = @import("std").testing;
|
|
|
|
fn test__fixunsdfsi(a: f64, expected: u32) void {
|
|
const x = __fixunsdfsi(a);
|
|
testing.expect(x == expected);
|
|
}
|
|
|
|
test "fixunsdfsi" {
|
|
test__fixunsdfsi(0.0, 0);
|
|
|
|
test__fixunsdfsi(0.5, 0);
|
|
test__fixunsdfsi(0.99, 0);
|
|
test__fixunsdfsi(1.0, 1);
|
|
test__fixunsdfsi(1.5, 1);
|
|
test__fixunsdfsi(1.99, 1);
|
|
test__fixunsdfsi(2.0, 2);
|
|
test__fixunsdfsi(2.01, 2);
|
|
test__fixunsdfsi(-0.5, 0);
|
|
test__fixunsdfsi(-0.99, 0);
|
|
test__fixunsdfsi(-1.0, 0);
|
|
test__fixunsdfsi(-1.5, 0);
|
|
test__fixunsdfsi(-1.99, 0);
|
|
test__fixunsdfsi(-2.0, 0);
|
|
test__fixunsdfsi(-2.01, 0);
|
|
|
|
test__fixunsdfsi(0x1.000000p+31, 0x80000000);
|
|
test__fixunsdfsi(0x1.000000p+32, 0xFFFFFFFF);
|
|
test__fixunsdfsi(0x1.FFFFFEp+31, 0xFFFFFF00);
|
|
test__fixunsdfsi(0x1.FFFFFEp+30, 0x7FFFFF80);
|
|
test__fixunsdfsi(0x1.FFFFFCp+30, 0x7FFFFF00);
|
|
|
|
test__fixunsdfsi(-0x1.FFFFFEp+30, 0);
|
|
test__fixunsdfsi(-0x1.FFFFFCp+30, 0);
|
|
|
|
test__fixunsdfsi(0x1.FFFFFFFEp+31, 0xFFFFFFFF);
|
|
test__fixunsdfsi(0x1.FFFFFFFC00000p+30, 0x7FFFFFFF);
|
|
test__fixunsdfsi(0x1.FFFFFFF800000p+30, 0x7FFFFFFE);
|
|
}
|