ruff/crates/ty_python_semantic/resources at 905b9d7f515ff4b093a9a55997e1855b54e2d73a - language-servers/ruff

mirror of https://github.com/astral-sh/ruff.git synced 2025-10-28 10:50:26 +00:00

History

David Peter 905b9d7f51 Some checks are pending CI / mkdocs (push) Waiting to run Details CI / Determine changes (push) Waiting to run Details CI / cargo fmt (push) Waiting to run Details CI / cargo clippy (push) Blocked by required conditions Details CI / cargo test (linux) (push) Blocked by required conditions Details CI / cargo test (linux, release) (push) Blocked by required conditions Details CI / cargo test (windows) (push) Blocked by required conditions Details CI / cargo test (wasm) (push) Blocked by required conditions Details CI / cargo build (release) (push) Waiting to run Details CI / formatter instabilities and black similarity (push) Blocked by required conditions Details CI / cargo build (msrv) (push) Blocked by required conditions Details CI / cargo fuzz build (push) Blocked by required conditions Details CI / fuzz parser (push) Blocked by required conditions Details CI / test scripts (push) Blocked by required conditions Details CI / test ruff-lsp (push) Blocked by required conditions Details CI / ecosystem (push) Blocked by required conditions Details CI / Fuzz for new ty panics (push) Blocked by required conditions Details CI / cargo shear (push) Blocked by required conditions Details CI / python package (push) Waiting to run Details CI / pre-commit (push) Waiting to run Details CI / check playground (push) Blocked by required conditions Details CI / benchmarks-instrumented (push) Blocked by required conditions Details CI / benchmarks-walltime (push) Blocked by required conditions Details [ty Playground] Release / publish (push) Waiting to run Details [ty] Reachability analysis for `isinstance(…)` branches (#19503 ) ## Summary Add more precise type inference for a limited set of `isinstance(…)` calls, i.e. return `Literal[True]` if we can be sure that this is the correct result. This improves exhaustiveness checking / reachability analysis for if-elif-else chains with `isinstance` checks. For example: ```py def is_number(x: int \| str) -> bool: # no "can implicitly return `None` error here anymore if isinstance(x, int): return True elif isinstance(x, str): return False # code here is now detected as being unreachable ``` This PR also adds a new test suite for exhaustiveness checking. ## Test Plan New Markdown tests ### Ecosystem analysis The removed diagnostics look good. There's [one case](`f52c4f1afd/torchvision/io/video_reader.py (L125-L143)`) where a "true positive" is removed in unreachable code. `src` is annotated as being of type `str`, but there is an `elif isinstance(src, bytes)` branch, which we now detect as unreachable. And so the diagnostic inside that branch is silenced. I don't think this is a problem, especially once we have a "graying out" feature, or a lint that warns about unreachable code.		2025-07-23 13:06:30 +02:00
..
corpus	[ty] Fix panic for attribute expressions with empty value (#19069 )	2025-07-09 08:46:33 +02:00
mdtest	[ty] Reachability analysis for `isinstance(…)` branches (#19503 )	2025-07-23 13:06:30 +02:00
primer	[ty] Upgrade mypy_primer (#19207 )	2025-07-08 15:56:54 +01:00
README.md

README.md

Markdown files within the mdtest/ subdirectory are tests of type inference and type checking; executed by the tests/mdtest.rs integration test.

See crates/ty_test/README.md for documentation of this test format.