Custom lints for my crates

I would like to create some custom lints for crates I'm planning on writing, how/where would you recommend creating them?

Clippy might not be the best place since the lints don't apply to general Rust code, but just to code using my crates. Rustc plugins are apparently deprecated and shortly going to be removed. rust-analyzer is apparently not a reliable place to lint for things that require knowing types and not just syntax.

I don't think this is possible, although I would be very happy to be proven wrong.

Besides basically rewriting clippy that is.

I believe it's technically possible via compiler plugins as you noted (I haven't heard that they'll be removed). Aside from that, I'm not aware of anything. Any approach would take a very large amount of effort, regardless.

You could use a procedural macro:
In a crate my_lint:

// Cargo.toml
proc-macro = true

quote = "1.0"
syn = { version = "1.0", features = ["visit", "full"] }
proc-macro-error = "1.0"
use proc_macro::TokenStream;
use proc_macro_error::{abort, proc_macro_error};
use quote::quote;
use syn::{
    visit::{self, Visit},
    ItemFn, Local,

/// Abort compilation if a `let` binding of the form
/// `let x: Type;` is found
pub fn abort_not_assigned(_metadata: TokenStream, input: TokenStream) -> TokenStream {
    let input = parse_macro_input!(input as ItemFn);
    let mut linter = Linter;

struct Linter;

impl<'ast> Visit<'ast> for Linter {
    fn visit_local(&mut self, local: &'ast Local) {
        if local.init.is_none() {
            abort!(local, "not assigned !")
        visit::visit_local(self, local);

And in mycrate:

// Cargo.toml
my_lint = { path = "path/to/my_lint" }
use my_lint::abort_not_assigned;

pub fn will_abort() -> i32 {
    let x: i32;
    x = 5;

pub fn will_not_abort() -> i32 {
    let x = 5;

There are some drawbacks however:

  • From what I gather there is currently no other option than emitting a hard error, so this is a pretty hardcore linter
  • All functions that you want linted need to be annotated with #[abort_not_assigned]
  • The linting is only based on syntax, not semantics, so this approach is very limited :frowning:
  • This might greatly increase compilation times

Sidenote : there is a #[must_use] attribute one could use for this specific case.