-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Reverse dependency between clippy_utils
and clippy_config
#13691
Conversation
This PR is best reviewed by just reviewing the first 2 commits. The last commit is just an automated renaming using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks! ❤️
clippy_config/src/lib.rs
Outdated
extern crate rustc_ast; | ||
extern crate rustc_attr; | ||
#[allow(unused_extern_crates)] | ||
extern crate rustc_driver; | ||
extern crate rustc_errors; | ||
extern crate rustc_session; | ||
extern crate rustc_span; | ||
extern crate smallvec; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like the removal of these dependencies (although they seemed to not be used, so I'm not sure if they ended up being linked to in the final executable).
I'm currently looking into the possibility of if being tied to rustc_driver*.so could be slowing us down by a considerable factor.
Follow up to #13691 Adds metadata to the `clippy_utils/Cargo.toml`, which is mostly copied from the root `Cargo.toml`. Adds a `README.md` file listing the nightly version `clippy_utils` can be used with, mentions that there are no stability guarantees and the license. The next PR will add automation to update the nightly toolchains in those files and the versions in the `Cargo.toml`s. cc #13556 changelog: none
In preparation of #13556, I want to remove the dependency on
clippy_config
, as I don't think that we want to publish that for outside consumers. To do this the 2 dependecies onclippy_config
had to be removed:clippy_config
, but was required inqualify_min_const
. I think exposing the MSRV infrastructure and the MSRVs we defined might also be helpful forclippy_utils
users. I don't see why it should not be able to live inclippy_utils
from a technical point of few.create_disallowed_map
function that took in aclippy_utils::types::DisallowedPath
is moved to theDisallowedPath
implementation. This also fits there and is only useful for Clippy and not inclippy_utils
for external consumers.clippy_config
now depends inclippy_utils
, so the dependecy just got reversed. But having theclippy_utils
crate as the base of the dependency tree in Clippy makes sense.changelog: none