Wooster
Wooster
The other two functions `shuffle` and `shuffleWithIndex` seem to be a very similar case so maybe we can have the same docs for them too just like above? Linking between...
I've already gone through this in my PRs: #12079 #13085 #13148 https://github.com/ziglang/zig/pull/13148#issuecomment-1283084057 https://github.com/ziglang/zig/commit/1952dd6437a73e3de211b649924a55fcb6e030be The status is that there's some weird issue going on that caused my main PR to be...
That "weird issue" is very likely coming from this function https://github.com/ziglang/zig/pull/12079/files#diff-f05e9ed61d2716c50e09b00c1881f44cdb2a85107d1b5c95231f80e489ea265eR225 which uses ESC[6n that @mitchellh mentioned. It messes with termios which would be great if we could avoid it...
@nektro doesn't work if you have multiple `std.Progress` instances from different processes (they can't communicate with each other) so if you do `ESC[0K` you might clear the progress of some...
Here's how my PR determines the optimal width to use for the terminal when a `std.Progress` is created: https://github.com/ziglang/zig/pull/12079/files#diff-f05e9ed61d2716c50e09b00c1881f44cdb2a85107d1b5c95231f80e489ea265eR179-R181 It gets the terminal width and then the position of the...
That would involve communication between entirely separate processes right? For example if you have multiple separate `zig` invocations. I think in that case the solution of getting the terminal cursor's...
Today I tested my implementation on Windows as well and using `SetConsoleCtrlHandler` worked just as expected. The program keeps running after the handler is run. Now I will just wait...
Well, I suspect the CI failure might be related and after double-checking a bunch of stuff I'm not yet sure what could be causing it, but maybe it will resolve...
Well, I'm not sure what's causing these CI failures. If I look at https://cloud.drone.io/ziglang/zig/22186/1/3 then it seems I should be able to reproduce locally using `zig build test-behavior -Dskip-non-native --zig-lib-dir...
As a side note I think it might be useful if we refactor `std.fmt.format` so that we can reuse most of its parsing code etc. in `std.fmt.scan`.