Eric Laurent comments

Results 7 comments of


                                            Eric Laurent

prevent confusing debugging experience when users write garbage to stdout, interfering with the build runner / test runner protocol

If for any reason a function is displaying something then it will be blocked, e.g.: const std = @import("std"); fn t() u8 { const writer = std.io.getStdOut().writer(); var buffered_writer =...

prevent confusing debugging experience when users write garbage to stdout, interfering with the build runner / test runner protocol

Not sure to understand what you are looking for. But for instance, simple logging to stdOut. The code shared is a simplified version to show the issue. The solution to...

prevent confusing debugging experience when users write garbage to stdout, interfering with the build runner / test runner protocol

(Un)fortunately, in this particular case, the library I translated is using its own logging framework and it relies on stdout. I think that the IPC between the build exe and...

prevent confusing debugging experience when users write garbage to stdout, interfering with the build runner / test runner protocol

It is not confusion but test run never exits.

prevent confusing debugging experience when users write garbage to stdout, interfering with the build runner / test runner protocol

Hi @andrewrk. Any progress on runner and builder communication design? It is very problematic to me that this issue is not recognized as a fundamental flaw in the current test...

prevent confusing debugging experience when users write garbage to stdout, interfering with the build runner / test runner protocol

@HeCorr, zig test and zig build test are not exactly the same. https://zig.news/slimsag/my-hopes-and-dreams-for-zig-test-2pkh

prevent confusing debugging experience when users write garbage to stdout, interfering with the build runner / test runner protocol

Once again, it has nothing to do with "unit tests which are not supposed to have side effects" or "who has the main() function decides". It has to do with...