#marker #lint


Marker's API, designed for stability and usability

11 releases (4 breaking)

new 0.4.3 Dec 2, 2023
0.4.2 Nov 25, 2023
0.3.0 Oct 5, 2023
0.2.1 Aug 24, 2023
0.0.0-placeholder Nov 4, 2022

#61 in Development tools

Download history 82/week @ 2023-08-18 50/week @ 2023-08-25 22/week @ 2023-09-01 22/week @ 2023-09-08 22/week @ 2023-09-15 16/week @ 2023-09-22 67/week @ 2023-09-29 123/week @ 2023-10-06 77/week @ 2023-10-13 2289/week @ 2023-10-20 2363/week @ 2023-10-27 2284/week @ 2023-11-03 2455/week @ 2023-11-10 2341/week @ 2023-11-17 2933/week @ 2023-11-24 2575/week @ 2023-12-01

10,719 downloads per month
Used in 4 crates



Marker API

Crates.io License: MIT OR Apache-2.0

marker_api provides a representation of the AST and all connected types needed to create custom lint crates for Marker, an experimental linting interface for Rust.


Marker is in the early stages of development, some things are still missing and the API still unstable.

A list of limitations and planned features can be found in Marker's Readme.


  • Stability: Marker's API design focuses on stability and expendability. The goal is to archive backwards compatibility, so that any lint, written after version 1.0.0, will compile and continue to work for years to come.
  • Usability: Marker's API focuses on usability, where possible under the constraints of Marker's stability guarantees. Types follow common design patterns and naming conventions, allowing you to focus on the lint logic directly.
  • Driver Independent: Every code analysis requires a driver that parses the code and provides further information. Marker's API is designed to be driver-independent, allowing it to support future compilers and potentially IDEs. (Currently, rustc is the only available driver)


This section will cover how you can set up your own lint crate. If you only want to run custom lints, checkout Marker's CLI interface cargo_marker. The rest of the section assumes that you have cargo_marker installed.


The simplest way to get started, is to use Marker's lint crate template, which already includes all dependencies, example code, and a working test setup.

Manual Setup


To get started, create a new Rust crate that compiles to a library (cargo init --lib). Afterwards, edit the Cargo.toml to compile the crate to a dynamic library and include marker_api as a dependency. You can simply add the following to your Cargo.toml file:

crate-type = ["cdylib"]

marker_api = "0.4.3"
marker_utils = "0.4.3"


The lint crate needs to provide an implementation of the LintPass trait and call the marker_api::export_lint_pass macro with the implementing type. Here is the minimal template:

use marker_api::prelude::*;
use marker_api::{LintPass, LintPassInfo, LintPassInfoBuilder};

// This is the struct that will implement the `LintPass` trait.
struct MyLintPass;

// This macro allow Marker to load the lint crate. Only one lint pass can be
// exported per lint crate.

// This macro declares a new lint, that can later be emitted
marker_api::declare_lint! {
    /// # What it does
    /// Here you can explain what your lint does. The description supports normal
    /// markdown.
    /// # Example
    /// ```rs
    /// // Bad example
    /// ```
    /// Use instead:
    /// ```rs
    /// // Good example
    /// ```

// This is the actual `LintPass` implementation, which will be called by Marker.
impl LintPass for MyLintPass {
    fn info(&self) -> LintPassInfo {

Now you can implement different check_* function in the LintPass trait.


To automatically test your lints, you might want to check out the marker_uitest crate.

And that's it. Happy linting!


Contributions are highly appreciated! If you encounter any issues or have suggestions for improvements, please check out Marker's GitHub repository.


Copyright (c) 2022-2023 Rust-Marker

Rust-Marker is distributed under the terms of the MIT license or the Apache License (Version 2.0).