ruff/crates/red_knot
Carl Meyer 8fe2dd5e03
[red-knot] pull primer projects to run from file (#17473)
## Summary

The long line of projects in `mypy_primer.yaml` is hard to work with
when adding projects or checking whether they are currently run. Use a
one-per-line text file instead.

## Test Plan

Ecosystem check on this PR.
2025-04-18 21:20:18 +00:00
..
docs [red-knot] pull primer projects to run from file (#17473) 2025-04-18 21:20:18 +00:00
src dependencies: switch from chrono to jiff 2025-04-15 07:47:55 -04:00
tests [red-knot] Add support for overloaded functions (#17366) 2025-04-18 09:57:40 +05:30
build.rs [red-knot] Add version command (#15823) 2025-02-02 18:56:51 +00:00
Cargo.toml dependencies: switch from chrono to jiff 2025-04-15 07:47:55 -04:00
README.md Add red_knot/README.md (#16230) 2025-02-18 23:31:02 -08:00

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.