-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Linting public reexport of private dependencies #143856
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
rustbot has assigned @compiler-errors. Use |
r? petrochenkov perhaps |
This comment was marked as resolved.
This comment was marked as resolved.
See calls to |
070e53d
to
d2fc98c
Compare
@rustbot label -S-waiting-on-author +S-waiting-on-review |
a0d9f53
to
d6ea20e
Compare
d6ea20e
to
d627e25
Compare
Thanks! |
Part of public/private dependencies #44663
Partially addresses #71043
I'm adding a warning for reexports of private dependencies into
rustc_resolve
. I get that this should not be a warning, but should instead be a lint to be controlled by the feature gate, but I did not figure out how exactly to do that at that point. I tried doing the same thing as is done inrustc_privacy
, but the linting system is not ready yet as far as I understand the error I got, so I made a warning for now instead. Some guidance on how to emit lints withdcx
would be appreciated.This also sets the
std_detect
crate as a public dependency ofstd
because some macros are reexported from there. I did not check closer, but the other option may be to allow the specific reexports instead.