Jake Goulding

> I think we should use the most recent version of a crate (if we use that crate at all), but I see no problem with keeping old versions around...

Which editor?  Which operating system? Assuming you are using Ace, can you reproduce it on https://ace.c9.io/build/kitchen-sink.html

You'll need to [file the issue with Ace, please](https://github.com/ajaxorg/ace). Feel free to link to the Ace issue from here once opened.

> I missed the small link Yeah, you'd be surprised at how many people don't read the template before opening an issue.

> The downside is needing UI for this, and needing to `rustup target add` on the playground servers Does `cargo miri setup` need to be run for each target?

> happens automatically when needed If I'm understanding you correctly, that'd be a bad thing on the playground, as the setup we do now takes ~150 seconds which would blow...

So to make this performant, we'd need to do this when pre-building the container: ``` cargo miri setup --target=x86_64-unknown-linux-gnu cargo miri setup --target=powerpc-unknown-linux-gnu ... ``` Once for each playground-supported target....

Maybe, I dunno! I assume that's changed over time and the build has never been updated since it worked: https://github.com/integer32llc/rust-playground/blob/d03009c20002b21d76f2f01b1efdd2749a0559f1/compiler/miri/Dockerfile#L6-L8

You will need to submit a pull request to the [Ace editor](https://ace.c9.io/).

I like to leave these open to keep tabs on things we will need to update eventually. 😉