Ivan Petkov

@hawkw we should probably extend this model to `JoinSet` as well (return custom errors instead of `io::Error`) EDIT: we should apply this to the `JoinSet` _builder_ which is still unstable

> If the spawn functions have different ways in which they can fail, then I would prefer different error types. I'm pretty busy for the next week but I will...

Errors have been split out into: - `SpawnError` for "regular" `spawn` - `SpawnBlockingError` for `spawn_blocking` - `SpawnLocalError` for `spawn_local` This should give us the ability to evolve the different errors...

Looks like there is an extension trait in the standard library which allows [for setting arbitrary `creation_flags()`](https://doc.rust-lang.org/stable/std/os/windows/process/trait.CommandExt.html#tymethod.creation_flags) We can easily add the same API but I think that won't help...

Hmm no idea why a nightly toolchain would cause such failures, unless something has changed in the standard library which doesn't play nicely with tokio's integration. @marc2332 do you know...

With #4824 merged tokio will use synchronous file handles for doing I/O with child processes (read/write operations will be done using the blocking threadpool)

@dpc I've opened #150 to use artifact symlinking by default which should bring down space usage in the Nix store when lots of derivations are chained! > Smart. Worth giving...

I wonder if both the tarball and the zstd compression are finding ways to dedup common parts across all files. The current deduping strategy only dedups if the same file...

> I'm confused. "tarball" is "zstd compressed". Aren't these two the same thing? We do both here. `tar` knows how to combine a bunch of separate files into one big...

I ran out of bandwidth to work on this 😞 Going to close this as I was planning on starting over in a more targeted manner (plus it's fallen behind...