Add a Run button to every example about rust-cookbook HOT 4 CLOSED

The static lists I could go either way on. That is, if we want to say that the cookbook libs should be in the playground, I'm cool with that. We can add a whitelist easily. Then we could just accept a PR every time a library goes though the blitz. I don't know if we want to start with worrying about if this crate available or not - just assume all are. A thing that would change my mind would be if we know there are incompatibilities.

from rust-cookbook.

As discussed on Use the crates from the libz blitz? rust-lang/rust-playground#168 the integer32 rust playground team is willing to coordinate with us on the list of preloaded crates.

Cookbook would be also interested on a json list of supported crates that we could consume in runtime to (re)enable play buttons for given examples.

As suggested by @KodrAus one or both parties might expose static json lists via raw github content.
What is left is to discuss the details.

cc @shepmaster

from rust-cookbook.

I guess that I would prefer to treat the playpen as semi volatile remote resource as we might add some non blitz crates to cookbook examples and We might want to query the playpen for supported crates prior to enabling play buttons on per example basis.

Having a whitelist would be awesome as we would be able to setup a curation process for the crate list. And we would just push a PR once crate is within the Libz Blitz. Could you specify the form (and possibly create a whitelist stub where you'd like to have it located)

Unfortunately I'll not be able to followup on this for the next two weeks due to holidays but someone from blitz might take it up in the meantime

from rust-cookbook.

fixed by update of mdbook

from rust-cookbook.