Casey Rodarmor

> I'm one of the maintainers of `nushell` and am interested in a cross-platform wrapper for std::process::Command. We have a couple requirements and I was wondering if your crate supports...

@soenkehahn This seems like something we should support, but I wanted to check with before I started implementing it. I was thinking about how to test this, and the obvious...

Another way to do this would be to have something like `OptionInput`, analogous to `OptionFuture`. Something like: ```rust struct OptionInput(Option); // With a boolean condition: cmd_unit!("ls", OptionInput(condition.then("some-file"))); // With an...

I think they're probably both useful, I wouldn't mind having both.

I think we would need a wrapper type, since we can't due blanket impls due to the impl on `&I where I: Input`. This works: ```rust struct Inputs(I); impl Input...

> Out of curiosity, what exactly is the advantage of using `IntoIterator` over `Iterator` here? Usually, `Iterator` is implemented by a specialized iterator types, for example `std::vec::Iter` or `std::collections::hash_map::Keys`. `Vec`...

I wonder if there should be some kind of speedbump to prevent users from using it without realizing that it's platform-dependent, i.e. it doesn't work on windows. The `exec` function...

I think `cradle::unix` is probably good. It seems unlikely that we'd have arch-specific stuff, for example, that would make two levels necessary. I *think* that you only get that label...

I think there are crates for most of these things: - https://crates.io/crates/glob - https://crates.io/crates/globset - https://crates.io/crates/tilde-expand (WTFPL, a sign of high quality software) - https://docs.rs/shellexpand/2.1.0/shellexpand/ (Does `~` expansion and variable...

I think that's fair. I don't have a particular use case, it just seems like something that would be nice. What do you think about leaving issues like this open?...