ruff/crates/red_knot
Micha Reiser 8d16a5c8c9
[red-knot] Use web-time instead of FileTime::now (#16967)
## Summary

`std::time::now` isn't available on `wasm32-unknown-unknown` but it is
used by `FileTime::now`.

This PR replaces the usages of `FileTime::now` with a target specific
helper function that we already had in the memory file system.
Fixes https://github.com/astral-sh/ruff/issues/16966

## Test Plan

Tested that the playground no longer crash when adding an extra-path
2025-03-25 13:03:30 +00:00
..
docs [red-knot] Add mypy_primer usage documentation (#16679) 2025-03-12 16:47:10 +01:00
src Allow discovery of venv in VIRTUAL_ENV env variable (#16853) 2025-03-20 13:55:35 +00:00
tests [red-knot] Use web-time instead of FileTime::now (#16967) 2025-03-25 13:03:30 +00:00
build.rs [red-knot] Add version command (#15823) 2025-02-02 18:56:51 +00: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

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.