Soni L.

There are certainly a lot of alternatives to pick from, the only question is which one is most appropriate. We do wonder if `Closure` could bring about any additional benefits...

(any feedback on the updated version/etc? we kinda put some of the motivation in the summary and we're not sure how to split it back out but it's probably okay???...

It means we welcome anyone to edit the proposed RFC almost like it's a wiki. Because the "GAnarchy" thing we linked? It's basically a "wiki of git repos".

Sure, but it's not like "making a wiki for it" is the *expected* way of creating RFCs. :sweat_smile: We hope that's fine tho.

Hmm, why did this get such an overwhelmingly negative response? - - - Btw, future work could've included giving `&Closure` an `TryInto` or so. Tho we find it unlikely that...

What about a clone_all macro? Hygiene stops at passed-in identifiers. A macro can take that identifier and create a let binding with it. You can have `let $name = $name.clone()`....

So [this](https://github.com/BurntSushi/ripgrep/blob/7120f3225862f6c718a37a8616debaebd8c3d459/src/main.rs#L97-L105): ```rust let args = Arc::clone(args); let quiet_matched = quiet_matched.clone(); let paths_searched = paths_searched.clone(); let match_line_count = match_line_count.clone(); let paths_matched = paths_matched.clone(); let bufwtr = Arc::clone(&bufwtr); let mut buf...

Aaand I just make a crate for it. because y'know, I just *had* to. https://crates.io/crates/clone_all

@lukaspiatkowski I encourage ppl to fork the things I've made. The whole point of free software is the ability to fork things, so please fork my things! (I'm not sure...

That's even less readable. :/ Noise is having the same code snippet over and over again and not having it in a well-documented standalone function. Also, I don't think that...