-
Notifications
You must be signed in to change notification settings - Fork 910
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
Expose clippy-driver as an executable #1678
Comments
We can add proxies sure, all we'll need is some indication of if it'll be a "normal" proxy or if you'll need something special. If it's normal, then just give us the name you want and we can add it. If you do that pretty soon, we might even be able to get it into 1.17.0 which we'd like to release soon (and will then be entering a larger refactoring effort which will make 1.18.0 a longer way off). |
Just needs to be clippy-driver. Users should probably not invoke this themselves so feel free to give it another name, but just clippy-driver is fine. |
See #1679 |
We're working on moving cargo-clippy into cargo (rust-lang/rust-clippy#3837). As a part of this,
clippy-driver
will need to be exposed by rustup.Can clippy-driver be exposed into the bin folder as a shim? It's fine if it has a different name or something
The text was updated successfully, but these errors were encountered: