lang-rust

Finding undocumented pub items in Rust involves scanning crate boundaries for public functions, structs, enums, and traits, then flagging missing /// doc comments and //! module-level docs to repair documentation gaps.

Checking Rust doc comment conventions involves verifying that all pub items have outer /// doc comments and modules have inner //! comments or module declarations, ensuring public API surface documentation accuracy.

Yes, you can generate a doc coverage report for Rust APIs by analyzing pub visibility modifiers and crate boundaries, which detects public items and flags missing documentation according to Rust doc-comment conventions.

Yes, this works across Rust libraries by analyzing crate boundaries and module declarations to detect pub visibility, ensuring functions, structs, enums, and traits are properly documented throughout the entire codebase.

The best way to reduce documentation debt in large Rust codebases is to automate public item detection and enforce doc-comment conventions during refactors, systematically identifying missing /// and //! comments on pub items.

Rust module docs might not be recognized if they lack inner //! doc comments or proper module declarations, which are required alongside outer /// comments on pub items to ensure full API documentation conformance.