Skip to content

Revert "Automatically defines the clippy feature" #1057

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

Merged
merged 1 commit into from
Jun 29, 2016
Merged

Revert "Automatically defines the clippy feature" #1057

merged 1 commit into from
Jun 29, 2016

Conversation

mcarton
Copy link
Member

@mcarton mcarton commented Jun 29, 2016

This reverts commit d7ba66b.

It was causing problems with crates with:

#![cfg_attr(feature="clippy", plugin(clippy))]

Close #1055.

This reverts commit d7ba66b.

It was causing problems with crates with:

```rust
#![cfg_attr(feature="clippy", plugin(clippy))]
```
env::args().collect()
} else {
env::args().chain(Some("--sysroot".to_owned())).chain(Some(sys_root)).collect()
};

args.extend_from_slice(&["--cfg".to_owned(), r#"feature="clippy""#.to_owned()]);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's enough to leave out this line

@oli-obk oli-obk merged commit 5f6b982 into master Jun 29, 2016
@oli-obk oli-obk deleted the 1055 branch June 29, 2016 12:54
@crumblingstatue
Copy link

Aww man, I started utilizing this feature.

Is it possible to bring this feature back in some form in the future?
Like defining feature=cargo-clippy or something.

@crumblingstatue
Copy link

Hrm. I guess I can add an empty [features] clippy = [] to my Cargo.toml, and enable the feature manually when running clippy with cargo clippy --features=clippy

@mcarton
Copy link
Member Author

mcarton commented Jul 2, 2016

Yeah, the point was to not have people have to do that manually but it's easy to do.
The problem was that people were already using the name “clippy” for something slightly different. Maybe we could bring it back under another name that people don't already use 👍.

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

Successfully merging this pull request may close these issues.

3 participants