News for hackers. Stuff that matters.

A comment on Understanding Rust futures by going way too deep. Parent comment

Re:Understanding Rust futures by going way too deep by gmac on Monday July 26, 2021 @07:36AM (#27958194)
Preferably the author doesn't copy and paste: preferably there's a documentation build step where everything gets run, relevant outputs get inserted into the docs, and any errors get caught.

This is how my docs for Zapatos[1] work, for instance. :)

[1] https://jawj.github.io/zapatos/

[ Parent | on HN ]
Re:Understanding Rust futures by going way too deep by j1elo on Monday July 26, 2021 @08:23AM (#27958521)
It is probably too much to ask everyone follow the same approach, so I'll be happy if people just test their own commands by hand. But your doc build step that validates code and catches errors? That's the ideal setup, for sure. Great job!
[ Parent | on HN ]