Jon Pretty

I think the solution, at least from a social perspective, is to make authoring a blog or tutorial which includes all the appropriate package names easier than authoring a blog or tutorial which omits them.https://twitter.com/propensive/status/1201177788247683072 …

How could that possibly be? Well, nobody writes examples without doing some form of checking on them. Having a compiler check the examples is already easier than compiling them (reliably) in your head, and it forces you to provide all necessary context.

So, to be easier overall, it "just" needs to be made easy to check the code fragments embedded within some text (in whatever form), without forcing the author to jump through too many hoops to set everything up. I have a background process running in my brain working on this.

That’s mdoc and doctests. Classpath, dependencies... are handled by the build tool, exactly like for tests or regular compilation- in fact, doctest is fairly straightforward codegen for plain, standard tests.