Skip to content
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

Closed
Manishearth opened this issue Mar 3, 2019 · 3 comments
Closed

Expose clippy-driver as an executable #1678

Manishearth opened this issue Mar 3, 2019 · 3 comments

Comments

@Manishearth
Copy link
Member

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

@kinnison
Copy link
Contributor

kinnison commented Mar 3, 2019

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).

@Manishearth
Copy link
Member Author

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.

@kinnison
Copy link
Contributor

kinnison commented Mar 4, 2019

See #1679

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants