Rain

Thanks! (I tried looking for a ticket but I couldn't find one -- totally might have missed it.) I'm happy to give it a go if that works for you...

Yes, I've come to believe that using / as the canonical relative path separator, and \ as the canonical absolute path separator, makes the most sense on Windows.

Note that using a pidfd will cause libstd to fall back to the relatively slow `fork`/`exec` over the faster `posix_spawn`. The difference is quite measurable (2-3x for the clap repo,...

Hi there, thanks for the feature request! I think this gets complicated really soon: * just the standard none/default/all features or the full power set of features * exclude certain...

BTW if you want to build something like this yourself, check out https://crates.io/crates/guppy, another thing I wrote (which nextest uses, in fact!)

Thanks! I totally agree it's valuable for the community, I just don't think nextest itself should implement it internally. If someone else (like yourself!) implements this as a [library/binary pair](https://rust-cli-recommendations.sunshowers.io/binaries-vs-libraries.html)...

Thanks for the feature request! Tests are currently output in the order they finish. I think it's totally reasonable to request that they be output in the order they were...

Thanks for offering to help! > sure. what would that look like? i can see i would need to add the option in the cli and then in the builder....

BTW I wouldn't make this a config option, just a CLI flag: `--status-order finished/started`. (`finished` is the current default, `started` is what you're asking for)

Thinking about this more, I realized a couple of things: * I'm not sure how this would interact with failing-fast (cancel the run as soon as the first failure happens)....