Browse Teach Curate

Modules, Paths, and Visibility in Rust

Modules split a program into named parts, and visibility rules decide which parts of each module the outside world may touch. Anything not marked public stays private to its module, so you can change it later without breaking other code. This is how a large codebase keeps its internal details from leaking.

Questions this Concept answers

Why does the `kernel` crate keep its raw `bindings` module out of reach of driver code?

jeremy Video

Rust Modules and Crates: pub, use, and Cargo Workspaces

Rust organizes code into a hierarchy of modules, where items are private by default and visibility must be explicitly widened via graduated access levels (public within the defining module, within th…