Feature request: validate sample code in documentation

[Vectornaut]

Feature request

Some documentation errors (for example, issue #77) can be caught by validating sample code. Three possible levels of validation are:

• Compile the sample code and check for errors and warnings.
• Run the sample code and check for panics.
• Use assertions in the sample code to validate behavior.

I've put in checkboxes to indicate which levels Rwf supports so far.

Implementation ideas

I don't think MkDocs has built-in validation tools like rustdoc does, but the mkdocs-code-validator plug-in might work.

[Vectornaut]

Manually validating the corrected code samples in pull request #77 makes it clear that this would be more complicated than just compiling and running each sample separately. For that pull request, I had to merge two different code samples to get a runnable program. I'm not sure whether mkdocs-code-validator supports stuff like that. The rustdoc validation tools don't seem to: their manual suggests copying the whole program into each sample and then hiding everything except the lines that each sample is supposed to show.