-
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
Remove extern crate clippy_lints
from tests
#4784
Conversation
Looks like some tests are still failing..? (or broke again in the meantime) |
This shouldn't be necessary, see rust-lang/rust#66158 (comment) |
#[macro_use] | ||
extern crate clippy_lints; | ||
|
||
declare_clippy_lint! { |
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.
Instead of removing this test, we can change this to the declare_lint
macro from rustc. The intend of this test would persist.
7452283
to
4721f44
Compare
📌 Commit 4721f44 has been approved by |
Remove `extern crate clippy_lints` from tests This causes rustc's build system to fail because it still tries to load the crate as a plugin: rust-lang/rust#66158 (comment) . I'm not sure _why_ this happens, but for a short term fix we should remove these. In one case it was just a convenient crate to use so i picked a different test. In another it was load-bearing, I had to delete the test. Idk if there's a better way around this. changelog: none
☀️ Test successful - checks-travis, status-appveyor |
This causes rustc's build system to fail because it still tries to load the crate as a plugin: rust-lang/rust#66158 (comment) . I'm not sure why this happens, but for a short term fix we should remove these.
In one case it was just a convenient crate to use so i picked a different test. In another it was load-bearing, I had to delete the test. Idk if there's a better way around this.
changelog: none