I've looked a bit at the API documentation for Rust. I was surprised to see that very often the documentation for a method uses one or more assert...
For further actions, you may consider blocking this person and/or reporting abuse
There is a good reason for that: cargo test checks doctests too. If the method will break, the doctest will panic and the build will break. This is like more unit tests. This also serves as a proof that the documentation is correct, AKA "if it compiles, it works".
Interesting. I've done something similar in a Ruby project (don't remember which one -- I'm 79), by having a Rake task that makes the doc by running examples, then including the code and output into the doc.