> Perhaps there's merit to having runnableExamples: and runnableTests: , the > former copied to docs and the latter not?
No matter what we call it, separating doc example code from actual tests is a good thing: * Regular source code of a module should be validated against tests with a testing framework/convention. * Doc example code should be validated against regular source code by the doc generator. * Some testing code is good example code, but not all of it, and vice versa. @timothee said in the original thread that D can generate tests into the docs (optionally?), so somebody thought about this and it sure sounds nice.
