Jake Goulding

I kind of feel like there's going to be an infinite amount of these, considering that any FFI function won't be supported. I don't have a good solution other than...

> Does this try to spawn a thread later I... literally have no idea ;-) This was just the first non-trivial thing I thought to test the playground's support of...

> version `0.4.1` through `0.4.4` fail to compile. Yes, that's caused by #39. TL;DR, older versions of Rust exposed the SIMD intrinsics in one way, that was changed, and a...

> a new version was released — technically semver incompatible. If you have a proposal for a semver **compatible** implementation of 0.4.x that compiles with modern Rust, then we could...

My naïve expectation is that a macro would get a lot of the way there: `*pm!(o->middle->inner->a) = 1;`. Since this hasn't been mentioned in the RFC or comments yet, there...

> make it easier to create a wrapper type The keyword there is *delegation*. For example, https://github.com/rust-lang/rfcs/pull/2393 and https://github.com/rust-lang/rfcs/pull/1406.

Using tools possible today: ```rust let make_cmd = move || Command::new(if is_windows { "cmd" } else { "pkill" }); Box::new(move |program| { let mut cmd = make_cmd(); ```

> when we could use the same instance all the time What is the expected benefit of using one instance? I believe you will need to prove that benefit.

> It's weird that Command have [`env_clear()`](https://doc.rust-lang.org/std/process/struct.Command.html#method.env_clear) while `args_clear()` is missing `env_clear` says (emphasis mine): > Clears all explicitly set environment variables **and prevents inheriting any parent process environment variables**....

> I'd like this to enable consts containing anonymous types, which are currently impossible. That's not required to support this case: ```rust // 1.41.0-nightly (2019-11-24 412f43ac5b4ae8c3599e) #![feature(impl_trait_in_bindings)] const VERSION: impl...