Tracking issue for future-incompatibility lint pub_use_of_private_extern_crate
#127909
Labels
A-crates
Area: Crates and their interactions (like crate loading)
A-lints
Area: Lints (warnings about flaws in source code) such as unused_mut.
A-resolve
Area: Name/path resolution done by `rustc_resolve` specifically
A-visibility
Area: Visibility / privacy
C-future-incompatibility
Category: Future-incompatibility lints
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
The
pub_use_of_private_extern_crate
lint detects a specific situation of re-exporting a privateextern crate
:A public
use
declaration should not be used to publicly re-export a privateextern crate
.pub extern crate
should be used instead.This was historically allowed, but is not the intended behavior according to the visibility rules.This used to be tracked as part of #34537, but is only tangentially related so it got a new dedicated tracking issue.
Related PRs
bitflags
are still in use.The text was updated successfully, but these errors were encountered: