Jake Goulding

> I'm concerned about the "unauthorized experimental collaborative process" you mentioned... It literally doesn’t matter because there is no “authorized” way of _creating_ an RFC.

This sounds like something that could be added to [calm_io](https://github.com/myrrlyn/calm_io) before being added to the standard library.

Actually, it's not clear what you mean by _failing_. Formatting to a string cannot fail at all beyond memory allocation. You also say "catch the compiler error", but then you...

> this would trigger an early return where I might want to continue working Use an IIFE (in stable) or a `try` block (in nightly): ```rust fn get_c(a: Option) {...

> You should already be able to import enum variants directly: That's true, but importing the variants can cause other name clashes: ```rust struct Fahrenheit(f32); struct Celcius(f32); enum Temperature {...

> macro could do all that boilerplate I can't find the one I'm thinking about, but I know that macros exist for this. A quick search found: - [capture](https://crates.io/crates/capture) -...

Or nikomatsakis' suggested form of the same, which places the borrow in the closest possible location, right when providing the closure: ```rust rayon::scope(|s| { for i in 0..10 { s.spawn({...

> Btw, in the meantime, there is a macro for this: There are many, as discussed in - https://github.com/rust-lang/rfcs/issues/2407#issuecomment-383244191 - https://github.com/rust-lang/rfcs/issues/2407#issuecomment-385291238 - https://github.com/rust-lang/rfcs/issues/2407#issuecomment-385198310

> `Box` I may be misunderstanding, but that would restrict futures to only the platforms that have liballoc. Futures already work on platforms where that’s not present, so that suggestion...

I see similar issues with a WAR. The `:git` gem is stored in `WEB-INF/gems/bundler/gems/`, whereas all the "normal" gems are in `WEB-INF/gems/gems/`. Loading the app results in the following error:...