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 __fixunsdfdi = @import("fixunsdfdi.zig").__fixunsdfdi;
|
|
const testing = @import("std").testing;
|
|
|
|
fn test__fixunsdfdi(a: f64, expected: u64) void {
|
|
const x = __fixunsdfdi(a);
|
|
testing.expect(x == expected);
|
|
}
|
|
|
|
test "fixunsdfdi" {
|
|
//test__fixunsdfdi(0.0, 0);
|
|
//test__fixunsdfdi(0.5, 0);
|
|
//test__fixunsdfdi(0.99, 0);
|
|
test__fixunsdfdi(1.0, 1);
|
|
test__fixunsdfdi(1.5, 1);
|
|
test__fixunsdfdi(1.99, 1);
|
|
test__fixunsdfdi(2.0, 2);
|
|
test__fixunsdfdi(2.01, 2);
|
|
test__fixunsdfdi(-0.5, 0);
|
|
test__fixunsdfdi(-0.99, 0);
|
|
test__fixunsdfdi(-1.0, 0);
|
|
test__fixunsdfdi(-1.5, 0);
|
|
test__fixunsdfdi(-1.99, 0);
|
|
test__fixunsdfdi(-2.0, 0);
|
|
test__fixunsdfdi(-2.01, 0);
|
|
|
|
test__fixunsdfdi(0x1.FFFFFEp+62, 0x7FFFFF8000000000);
|
|
test__fixunsdfdi(0x1.FFFFFCp+62, 0x7FFFFF0000000000);
|
|
|
|
test__fixunsdfdi(-0x1.FFFFFEp+62, 0);
|
|
test__fixunsdfdi(-0x1.FFFFFCp+62, 0);
|
|
|
|
test__fixunsdfdi(0x1.FFFFFFFFFFFFFp+63, 0xFFFFFFFFFFFFF800);
|
|
test__fixunsdfdi(0x1.0000000000000p+63, 0x8000000000000000);
|
|
test__fixunsdfdi(0x1.FFFFFFFFFFFFFp+62, 0x7FFFFFFFFFFFFC00);
|
|
test__fixunsdfdi(0x1.FFFFFFFFFFFFEp+62, 0x7FFFFFFFFFFFF800);
|
|
|
|
test__fixunsdfdi(-0x1.FFFFFFFFFFFFFp+62, 0);
|
|
test__fixunsdfdi(-0x1.FFFFFFFFFFFFEp+62, 0);
|
|
}
|