Mention unnameable_types
in unreachable_pub
documentation.
This link makes sense because someone who wishes to avoid unusable `pub` is likely, but not guaranteed, to be interested in avoiding unnameable types. Also fixed some grammar problems I noticed in the area. Fixes #116604.
This commit is contained in:
parent
b3b368a183
commit
2a96478dd8
2 changed files with 6 additions and 4 deletions
|
@ -1244,8 +1244,8 @@ impl<'tcx> LateLintPass<'tcx> for UngatedAsyncFnTrackCaller {
|
|||
|
||||
declare_lint! {
|
||||
/// The `unreachable_pub` lint triggers for `pub` items not reachable from other crates - that
|
||||
/// means neither directly accessible, nor reexported, nor leaked through things like return
|
||||
/// types.
|
||||
/// means neither directly accessible, nor reexported (with `pub use`), nor leaked through
|
||||
/// things like return types (which the [`unnameable_types`] lint can detect if desired).
|
||||
///
|
||||
/// ### Example
|
||||
///
|
||||
|
@ -1272,8 +1272,10 @@ declare_lint! {
|
|||
/// intent that the item is only visible within its own crate.
|
||||
///
|
||||
/// This lint is "allow" by default because it will trigger for a large
|
||||
/// amount existing Rust code, and has some false-positives. Eventually it
|
||||
/// amount of existing Rust code, and has some false-positives. Eventually it
|
||||
/// is desired for this to become warn-by-default.
|
||||
///
|
||||
/// [`unnameable_types`]: #unnameable-types
|
||||
pub UNREACHABLE_PUB,
|
||||
Allow,
|
||||
"`pub` items not reachable from crate root"
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue