We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

rustdoc: beyond documentation

Formal Metadata

Title
rustdoc: beyond documentation
Subtitle
All the goodies packed in rustdoc, and more
Title of Series
Number of Parts
490
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Rust compiler comes with a few tools, rustdoc is one of them. It is THE standard rust tool to generate documentation for your crates. Rust compiler comes with a few tools, rustdoc is one of them. It is THE standard rust tool to generate documentation for your crates. You can write documentation using "///" or "//!" patterns (which are syntaxic sugar over #[doc = "..."]). It generates HTML which can used locally without a need for internet connection. The documentation search is running in JS directly in your browser. You have a source code viewer integrated. You can pick different themes (and even add one yourself). It works with javascript disabled. It provides settings to make your docs browsing more comfortable. You can generate docs with extra content (take a look at https://docs.rs/pwnies for a good example!). But not only it generates documentation, it also adds things for each type that you didn't know was available thanks to the "Auto-traits implementation" and "Blanket implementation" sections. In addition to generate documentation, it provides functionalities such as an integrated documentation's test runner (which themselves can be quite customized!). It also provides lints that can you deny (missingdocs, missingdoc_example). With just all this, rustdoc is already a quite complete tool. But more will come in the future: more interactive source code viewer automatic link generation based on the item name more output formats supported (json would be the first) cfgs (doctest and doc) doc aliases for search (for instance, "*" proposes pointer in the std lib)