'Book' seems a grand title for what could essentially fit in a long blog post? One thing I've been wondering recently is in relation to Rust's overhead for dynamic bounds checks. I know in many cases these can be avoided/elided (e.g. using iterators), but are there any common cases where this isn't possible? Or alternatively where convincing the compiler to remove them introduces a significant amount of complexity?

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() } }')