mirror of https://github.com/astral-sh/ruff
1d49e71ddd
We weren't really using `chrono` for anything other than getting the current time and formatting it for logs. Unfortunately, this doesn't quite get us to a point where `chrono` can be removed. From what I can tell, we're still bringing it via [`tracing-subscriber`](https://docs.rs/tracing-subscriber/latest/tracing_subscriber/) and [`quick-junit`](https://docs.rs/quick-junit/latest/quick_junit/). `tracing-subscriber` does have an [issue open about Jiff](https://github.com/tokio-rs/tracing/discussions/3128), but there's no movement on it. Normally I'd suggest holding off on this since it doesn't get us all of the way there and it would be better to avoid bringing in two datetime libraries, but we are, it appears, already there. In particular, `env_logger` brings in Jiff. So this PR doesn't really make anything worse, but it does bring us closer to an all-Jiff world. |
||
|---|---|---|
| .. | ||
| docs | ||
| src | ||
| tests | ||
| Cargo.toml | ||
| README.md | ||
| build.rs | ||
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.