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
22 lines
761 B
Zig
22 lines
761 B
Zig
const __divti3 = @import("divti3.zig").__divti3;
|
|
const testing = @import("std").testing;
|
|
|
|
fn test__divti3(a: i128, b: i128, expected: i128) void {
|
|
const x = __divti3(a, b);
|
|
testing.expect(x == expected);
|
|
}
|
|
|
|
test "divti3" {
|
|
test__divti3(0, 1, 0);
|
|
test__divti3(0, -1, 0);
|
|
test__divti3(2, 1, 2);
|
|
test__divti3(2, -1, -2);
|
|
test__divti3(-2, 1, -2);
|
|
test__divti3(-2, -1, 2);
|
|
|
|
test__divti3(@bitCast(i128, u128(0x8 << 124)), 1, @bitCast(i128, u128(0x8 << 124)));
|
|
test__divti3(@bitCast(i128, u128(0x8 << 124)), -1, @bitCast(i128, u128(0x8 << 124)));
|
|
test__divti3(@bitCast(i128, u128(0x8 << 124)), -2, @bitCast(i128, u128(0x4 << 124)));
|
|
test__divti3(@bitCast(i128, u128(0x8 << 124)), 2, @bitCast(i128, u128(0xc << 124)));
|
|
}
|