Some slides contain "run"-buttons for code fragments which are not runable by themselves

[yarwelp]

One such example is slide num. 26 from lecture 01.

The code fragment given there is:

impl Point {
    fn new(x: i32, y: i32) -> Point {
        Point { x: x, y: y }
    }
}
fn main() {
    let p = Point::new(1, 2);
}

I suggest removing the "run" button from such examples which require additional code in order to run.

Alternatively, if possible, you might adjust the system somehow so that you can have the full code required to run the code fragment provided. Looking at how the system is built up, I suppose this could be a difficult thing to achieve. Perhaps if you include the full source of each snippet alongside the content.md files and you name them by the slide number they appear in and you include them as javascript strings and write a bit of javascript to pick the string that corresponds to a code fragment?

Probably just removing the run button for unrunable fragments makes the most sense with regards to amount of work.

Could also be that doing anything at all about the run buttons is more work than there is benefit from.

[terryxsun]

Ideally I'd like to do the same thing as rustdoc and/or rustbook -- by letting you include commented out context that doesn't display on the rendered version but is visible in the source/when you open in playpen.

This is vaguely on my todo list, but not one of my priorities right now.