Yep. I'll also add that "books" are typically used for higher-level, more narrative pieces of documentation, vs the API-level `rustdoc`-generated documentation.
Re:The Rust Performance Book
by anonymousDan on Tuesday November 17, 2020 @04:22PM
(#25130029)
Thanks for the links. If the intention is to expand over time then I agree it makes sense.
Rust Book: https://doc.rust-lang.org/book
Rust Rand Book: https://rust-random.github.io/book
Rust WebAssembly Book: https://rustwasm.github.io/book
Rust Unstable Book: https://doc.rust-lang.org/beta/unstable-book/index.html
Rustonomicon: https://doc.rust-lang.org/beta/nomicon/index.html
Cargo Book: https://doc.rust-lang.org/cargo
Which seems to be generated by https://github.com/rust-lang/mdBook
Now, I don't see why "book" should seem so grand. Remember when reference books would come out as a "bible"?
As for bounds check, here's a relevant issue raised on rand crate: https://github.com/rust-random/rand/issues/592
One can dig for a kind of "unsafe assertions" with https://doc.rust-lang.org/std/hint/fn.unreachable_unchecked.... (so the random code, for example, could have before returning value 'if x >= upper { unsafe { unreachable_unchecked() } }')