Jeff Anderson

this issue should be re-opened. It reproduces for me on any directory that exists. I think @WillLillis did not use a directory that exists but was still an otherwise invalid...

@Vexu You're right I couldn't get the exact same reproduction. Since the steps have changed, I created a separate issue: https://github.com/ziglang/zig/issues/22122

Looks like windows CI failure is https://github.com/ziglang/zig/issues/22510 ?

If we want to be more specific, we may want to reference some relevant standard or specifically declare that the clock is the number of "non-leap seconds" since the unix...

There seems to be precedent for using `@compileError` like I am. For example: https://github.com/ziglang/zig/blob/d23db9427b82d7dc798442accf34729c16e92f2d/lib/std/bit_set.zig#L322

@rohlem @rootbeer I'm not sure whether I should be clinking "resolve conversation". I would generally expect the conversation creator to click resolve when they feel it is resolved? Might be...

given that packed struct equality operator just got merged https://github.com/ziglang/zig/pull/21679 I will convert my tests to use `testing.expectEqual` instead of `testing.expectEqualDeep`, either as soon as I can finish building from...

> There seems to be precedent for using `@compileError` like I am. For example: > > https://github.com/ziglang/zig/blob/d23db9427b82d7dc798442accf34729c16e92f2d/lib/std/bit_set.zig#L322 switched to using `comptime unreachable` and relying on compiler to generate compile errors.

superseded by writergate https://github.com/ziglang/zig/pull/24329

Would adding a select few simplified (no printing etc) versions of these functions to `test/behavior.zig` be a satisfactory solution to the more complicated tests? For example, we could add `simpleExpectEqualStrings()`...