zig/test/behavior/bugs/1486.zig

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

const ptr = &global;
var global: u64 = 123;

test "constant pointer to global variable causes runtime load" {
    global = 1234;
    try expect(&global == ptr);
    try expect(ptr.* == 1234);
}
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-09 07:18:47 +08:00			`const expect = @import("std").testing.expect;`
stage1: unify 2 implementations of pointer deref I found out there were accidentally two code paths in zig ir for pointer dereference. So this should fix a few bugs. closes #1486 2018-09-22 06:47:12 +08:00
			`const ptr = &global;`
			`var global: u64 = 123;`

			`test "constant pointer to global variable causes runtime load" {`
			`global = 1234;`
update usage of std.testing in behavior and standalone tests 2021-05-05 02:23:22 +08:00			`try expect(&global == ptr);`
			`try expect(ptr.* == 1234);`
stage1: unify 2 implementations of pointer deref I found out there were accidentally two code paths in zig ir for pointer dereference. So this should fix a few bugs. closes #1486 2018-09-22 06:47:12 +08:00			`}`