Book is what this site layout is called in the community, see also: Rust Book: https://doc.rust-lang.org/book https://doc.rust-lang.org/book Rust Rand Book: h

Book is what this site layout is called in the community, see also: Rust Book: https://doc.rust-lang.org/book https://doc.rust-lang.org/book Rust Rand Book: https://rust-random.github.io/book https://rust-random.github.io/book Rust WebAssembly Book: https://rustwasm.github.io/book https://rustwasm.github.io/book Rust Unstable Book: https://doc.rust-lang.org/beta/unstable-book/index.html https://doc.rust-lang.org/beta/unstable-book/index.html Rustonomicon: https://doc.rust-lang.org/beta/nomicon/index.html https://doc.rust-lang.org/beta/nomicon/index.html Cargo Book: https://doc.rust-lang.org/cargo https://doc.rust-lang.org/cargo Which seems to be generated by https://github.com/rust-lang/mdBook 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 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.html 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() } }')