3 ms·
Clippy running on stable is quite far off. We've had discussions about stabilizing plugins, but it's not happening soon. Instead, make clippy an optional featu
by Manishearth 11y ago
Clippy running on stable is quite far off. We've had discussions about stabilizing plugins, but it's not happening soon.
Instead, make clippy an optional feature, and compile with `cargo build --features=clippy` on your CI on nightly.
- killercup 11y ago> make clippy an optional feature Yeah, that's what I'm doing but that is also the reason why nightly is an allowed failure on Travis… I have high hopes for compiler plugins after the current internal refactorings (HIR, MIR), though :)
- Manishearth 11y agoHIR/MIR don't really help much, actually. A stable plugin interface would probably be completely different. And clippy uses a _lot_ of internals, so even if a plugin interface stabilizes there's no guarantee clippy will.
- steveklabnik 11y agoMy understanding was that HIR was supposed to _be_ a stable plugin interface.
- Manishearth 11y agoPerhaps. There's still a long way to go though, since you need a stable AST builder or qquote mechanism, among other things. And HIR isn't nearly enough for clippy to work on stable.