zig/test/behavior/widening.zig

const std = @import("std");
const expect = std.testing.expect;
const mem = std.mem;

test "integer widening" {
    var a: u8 = 250;
    var b: u16 = a;
    var c: u32 = b;
    var d: u64 = c;
    var e: u64 = d;
    var f: u128 = e;
    try expect(f == a);
}
add casting docs, __extenddftf2, and __extendsftf2 2018-06-21 19:43:55 +01:00			`const std = @import("std");`
std.debug.assert: remove special case for test builds 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 2019-02-08 23:18:47 +00:00			`const expect = std.testing.expect;`
add casting docs, __extenddftf2, and __extendsftf2 2018-06-21 19:43:55 +01:00			`const mem = std.mem;`

			`test "integer widening" {`
			`var a: u8 = 250;`
			`var b: u16 = a;`
			`var c: u32 = b;`
			`var d: u64 = c;`
			`var e: u64 = d;`
			`var f: u128 = e;`
update usage of std.testing in behavior and standalone tests 2021-05-04 19:23:22 +01:00			`try expect(f == a);`
add casting docs, __extenddftf2, and __extendsftf2 2018-06-21 19:43:55 +01:00			`}`