You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Suggestion for pub(crate) not always valid on multiple imports #50455
I also wish we had a better answer for this lint than chopping up spans, but the current architecture makes this hard (this has been a problem for clippy forever).
The problem here is that when we do HIR lowering we split apart uses, and this totally breaks down.
But we throw away the AST by the time we have access level info.
We can skip this lint for pub use for now, but that's not too great.
#50476 proposes not making suggestions for use items. (The lint itself still fires, of course.)
I also wish we had a better answer for this lint than chopping up spans, but the current architecture makes this hard (this has been a problem for clippy forever).
Activity
Manishearth commentedon May 4, 2018
cc @zackmdavis who implemented this
I also wish we had a better answer for this lint than chopping up spans, but the current architecture makes this hard (this has been a problem for clippy forever).
The problem here is that when we do HIR lowering we split apart
uses, and this totally breaks down.But we throw away the AST by the time we have access level info.
We can skip this lint for
pub usefor now, but that's not too great.I don't really have ideas for fixing this.
zackmdavis commentedon May 6, 2018
#50476 proposes not making suggestions for
useitems. (The lint itself still fires, of course.)We could add spans to
hir::Visibility?Rollup merge of rust-lang#50476 - zackmdavis:tame_unreachable_pub_sug…
Auto merge of #50476 - zackmdavis:tame_unreachable_pub_suggestion, r=…
Auto merge of #51866 - zackmdavis:hir_making_each_day_of_the_year, r=…