mirrors/ruff
1
0
Fork 0
mirror of https://github.com/astral-sh/ruff.git synced 2025-07-24 05:25:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
ruff/crates/red_knot
History
Andrew Gallant 27a377f077 red_knot_python_semantic: migrate types/infer to new diagnostic model 
I gave up trying to do this one lint at a time and just (mostly)
mechanically translated this entire file in one go.

Generally the messages stay the same (with most moving from an
annotation message to the diagnostic's main message). I added a couple
of `info` sub-diagnostics where it seemed to be the obvious intent.
2025-04-22 12:08:03 -04:00
..
docs [red-knot] mypy_primer: Use upstream repo (#17500) 2025-04-22 11:55:16 +02:00
src dependencies: switch from chrono to jiff 2025-04-15 07:47:55 -04:00
tests red_knot_python_semantic: migrate types/infer to new diagnostic model 2025-04-22 12:08:03 -04:00
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

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.