Veikka Tuominen
Veikka Tuominen
It shouldn't be required.
Duplicate of #19473
Crash fixed by: ```diff diff --git a/src/psp/sdk/pspguimpl.zig b/src/psp/sdk/pspguimpl.zig index b835002..80e8903 100644 --- a/src/psp/sdk/pspguimpl.zig +++ b/src/psp/sdk/pspguimpl.zig @@ -8,7 +8,7 @@ test { } //Internals -pub const GuCallback = ?fn (c_int) callconv(.C)...
> I also have a minimal case for this one but I'm not sure where to add it to the tests: It's supposed to produce a compile error so `test/cases/compile_errors`...
Caused by this check which doesn't check inferred error set payload being generic poison: https://github.com/ziglang/zig/blob/2008d0f7c9cfb0ab5ea908c216751dbc335d1735/src/Sema.zig#L17855
> I don't know if this should introduce a dedicated AIR instruction instead of emitting two `int_from_ptr` and a `sub_wrap` I don't think a dedicated AIR instruction is needed (unless...
I think it needs to check that the pointers point to the same object for the operation to make sense at comptime. Otherwise it'll have to fall back to doing...
I'm not sure if the problem is `Value.ptrField` always returning a new `field` pointer or the base address check being too strict but I'd expect both of these to work:...
But it results in a wrong value since `Value.ptrField` always sets the `byte_offset` to `0`. ```zig pub fn main() void { var a: struct { a: u32, b: u32 }...
`fs.createFile` does take `fs.File.CreateFlags` with `truncate` but setting it to false is currently a no-op so it defaults to truncating either way.