Veikka Tuominen
Veikka Tuominen
#16698 was a duplicate of this.
`--summary failures` and default: ```sh-session $ zig build test steps [3/8] zig build-exe test-runner Debug native... LLVM Emit Object... Test [1/235] standard-place Test [34/235] initializers... 3 tests skipped Test [75/235]...
For the change in Zig CI failure see https://github.com/ziglang/zig/actions/runs/5227592809/jobs/9439336808
> Do you mean the type names are reversed? I think it makes sense. It's assigning to a value of type `*error{Bar,Foo}`, so it's expecting `*error{Bar,Foo}`, but found `*error{Foo}`. Yes...
>First of all it would be nice if the error indicator was on the void part. There is a TODO next to where that error is implemented stating that it...
> Sorry, I think that was my intention originally but I somehow thought it wasn't really possible to add a test for this but now thanks to your reminder I...
Could you add a test case to `parser_test.zig`?
This doesn't look like it can handle the pointer being wrapped in a `.opt_payload`, using `optionalValue` should solve that.
Is the sentinel always ignored or would `@bitCast(u64, "Locatio".*)` also work?