-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
Using items from a deprecated module does not warn #47237
Copy link
Copy link
Open
Labels
A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.Area: Lints (warnings about flaws in source code) such as unused_mut.A-resolveArea: Name/path resolution done by `rustc_resolve` specificallyArea: Name/path resolution done by `rustc_resolve` specificallyC-bugCategory: This is a bug.Category: This is a bug.L-deprecatedLint: deprecatedLint: deprecatedT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.Area: Lints (warnings about flaws in source code) such as unused_mut.A-resolveArea: Name/path resolution done by `rustc_resolve` specificallyArea: Name/path resolution done by `rustc_resolve` specificallyC-bugCategory: This is a bug.Category: This is a bug.L-deprecatedLint: deprecatedLint: deprecatedT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Attempting to
use deprecated_module;oruse deprecated_module::*;fails, but doinguse deprecated_module::SpecificItem;compiles with no error. Right now in Diesel I'm actually seeing an even more confusing error:Even though there is nothing in the project with that name. However, I'm unable to reproduce that issue outside of Diesel.
Regardless, the following code compiles without warnings, but should warn.