ruff/crates/red_knot
Andrew Gallant 2bcd2b4147 red_knot: plumb through `DiagnosticFormat` to the CLI
The CLI calls this `OutputFormat`, and so does the type where the CLI is
defined. But it's called `DiagnosticFormat` in `ruff_db` to be
consistent with `DisplayDiagnosticConfig`.

Ref https://github.com/astral-sh/ruff/issues/15697#issuecomment-2706477278
2025-03-14 14:46:17 -04:00
..
docs [red-knot] Add mypy_primer usage documentation (#16679) 2025-03-12 16:47:10 +01:00
src red_knot: plumb through `DiagnosticFormat` to the CLI 2025-03-14 14:46:17 -04:00
tests red_knot: plumb through `DiagnosticFormat` to the CLI 2025-03-14 14:46:17 -04:00
Cargo.toml [red-knot] Add argfile and windows glob path support (#16353) 2025-02-25 08:43:13 +01:00
README.md Add `red_knot/README.md` (#16230) 2025-02-18 23:31:02 -08:00
build.rs [red-knot] Add version command (#15823) 2025-02-02 18:56:51 +00:00

README.md

Red Knot

Red Knot is an extremely fast type checker. Currently, it is a work-in-progress and not ready for user testing.

Red Knot is designed to prioritize good type inference, even in unannotated code, and aims to avoid false positives.

While Red Knot will produce similar results to mypy and pyright on many codebases, 100% compatibility with these tools is a non-goal. On some codebases, Red Knot's design decisions lead to different outcomes than you would get from running one of these more established tools.

Contributing

Core type checking tests are written as Markdown code blocks. They can be found in red_knot_python_semantic/resources/mdtest. See red_knot_test/README.md for more information on the test framework itself.

The list of open issues can be found here.