For new or renamed modules, items, and public API paths, follow docs/naming-guide.md.
Default expectations:
- Prefer semantic module paths over flat prefixes.
- Do not force a single module level; use nested modules when each segment adds real meaning.
- Prefer concise public leaf names only when the parent path is already descriptive.
- If the parent path is weak or purely technical, keep more specificity in the item name or choose a better module path.
- Use
pub use ... as ...when internal names need more context but the public API should stay shorter. - Prefer import styles that keep the namespace visible at call sites when the qualifier adds net meaning.
- Do not preserve a qualifier mechanically. If the leaf already carries the category clearly and the qualifier mostly repeats it, prefer the shorter leaf.
- Treat lint suggestions as hypotheses, not commands. If satisfying a lint would make call sites noisier, tighten the lint instead of cargo-culting the style.