Jake Goulding

From the error log, it appears that your gist doesn't have a `description` field (`Error("invalid type: null, expected a string", line: 1, column: 2879)`). This is a mistake in [the...

I encourage you to use the crate autocomplete for that, as it includes the crate version:  otherwise, you can link to the current [Cargo.toml](https://github.com/integer32llc/rust-playground/blob/master/compiler/base/Cargo.toml). This is...

This is a semi-known issue. The short version is that your local version of the fonts are screwed up in some way (rust-lang/rust#16372; rust-lang/rust#34120). It should also be possible to...

This rather sounds like the editor keybinding style is set to Vim. Can you check in the config:  If that's not the case, can you try to reproduce that...

This is probably due to fact that playground has hundreds of crates that are always available and at least one of those crates links to the standard library. I’ve seen...

> No idea why this got a `wontfix` label. Because you used the [issue template](https://github.com/integer32llc/rust-playground/blob/master/.github/ISSUE_TEMPLATE/crate-addition-or-update.md) that contains the text: > Any issue opened for a new or updated crate version...

As stated in #531: > file an issue with rand. They can specify [metadata for extra features that they think should be enabled on the playground](https://github.com/integer32llc/rust-playground/issues/192#issuecomment-388589736) I think you might...

> either include the latest version of `rand_pcg` As stated multiple locations, including the issue template linked above, I don't want to get into the business of deciding which crates...

> why is use of outdated crates a problem in the first place didn’t you open this issue *because* of the use of an outdated crate? ("because having the playground...

> The error message here is confusing. You may also want to consider opening/adding to a Rust issue about this case as it applies to any user, not just the...