Jake Goulding

> In the meanwhile, do you think that the `let arg = arg.as_mut();` should already be in the code? I'm not the target audience of Rustlings, but my gut says...

Running this seemed to work well for me!

This was something we had discussed a long while ago, and I'm generally in favor. Some thoughts: 1. We should do it for all the tools 2. We should show...

Yes, this is the browser / GitHub doing it. For example:  I don't particularly relish attempting to subvert how the OS / browser / GitHub perform...

> unnecessarily verbose output in reports I did try to help with that case but was [requested to stop](https://github.com/integer32llc/rust-playground/issues/671).

> desire just the textual representation of errors This can be done *by the user* by using "Paste and Match Style" or the equivalent browser / OS options.

I can see your point of view, and I think something akin to `display(false)` would make sense. As a third avenue: ```rust #[derive(Debug, Snafu)] enum ExtractionError { #[snafu(display("failed to extract...

> can you use `format_args!` I had the same idea 😉. Unfortunately, the implementation of `format_args` is aggressive about references and you basically can never "return" it: ```rust fn main()...

> since there are probably other cases where custom `Display` implementations would help. Certainly. In fact, there’s been low level chatter about having some kind of `derive(Display)` in the standard...

> to translate errors would you mind chiming in on #254? If possible, I’d rather like to extend SNAFU to interact nicely with such functionality