ruff/crates/ty_python_semantic
Andrew Gallant bd5b7f415f ty_python_semantic: rejigger handling of overload error conditions
I found the previous code somewhat harder to read. Namely, a `for`
loop was being used to encode "execute zero or one times, but not
more." Which is sometimes okay, but it seemed clearer to me to use
more explicit case analysis here.

This should have no behavioral changes.
2025-05-14 11:13:41 -04:00
..
resources ty_python_semantic: update "no matching overload" diagnostic test 2025-05-14 11:13:41 -04:00
src ty_python_semantic: rejigger handling of overload error conditions 2025-05-14 11:13:41 -04:00
tests Use #[expect(lint)] over #[allow(lint)] where possible (#17822) 2025-05-03 21:20:31 +02:00
build.rs
Cargo.toml
mdtest.py
mdtest.py.lock