leongross
leongross
> but it's a bit harder than I expected to do correctly without race conditions how do you test for that systematically to detect them? Is there already a testing...
So if this turns out to be more tricky than initially anticipated it might be a good idea to first merge some stubbed implementations and then take on the more...
@aykevl any thoughts?
@aykevl I think the CI failure is just racy, maybe re-run it? Also, is there anything I can further help on?
What do you think about https://github.com/tinygo-org/tinygo/pull/4508 ?
@aykevl nix-ci seems to be broken due to llvm on [other branches as well](https://github.com/tinygo-org/tinygo/actions/runs/11291350989/job/31405090798?pr=4498#step:8:107)
@aykevl please rebase to fix the CI errors. EDIT: Updating the chromium driver go package seems to fix the wasm CI errors: * https://github.com/tinygo-org/tinygo/pull/4530 * https://github.com/tinygo-org/tinygo/pull/4531
Awesome that we got this finally merged, thanks, everyone!
#4417 was merged, maybe a rebase really is all it needs.
I think the general idea here is to be compatible with the original GNU coreutils, iputils and so on; especially in the user interface, so also the way the flags...