Things might be better now, but the previous false advertisement makes it really hard to tell. For example, vlang.io claims no undefined behaviour¹, but with struct Foo { bar int } println(&Foo(voidptr(some_address_here))) it seems to read whatever memory is at that address (which is UB in C, and V compiles to C, so...).

¹it says some overflowing can still result in UB, but that's not what's happening here; also this warning was only added in July.