Ibraheem Ahmed 1d6ae8596a [ty] Prefer exact matches when solving constrained type variables (#21165) ...

## Summary

The solver is currently order-dependent, and will choose a supertype
over the exact type if it appears earlier in the list of constraints. We
could be smarter and try to choose the most precise subtype, but I
imagine this is something the new constraint solver will fix anyways,
and this fixes the issue showing up on
https://github.com/astral-sh/ruff/pull/21070.

2025-10-31 10:58:09 -04:00

..

resources

[ty] Prefer exact matches when solving constrained type variables (#21165)

2025-10-31 10:58:09 -04:00

src

[ty] Prefer exact matches when solving constrained type variables (#21165)

2025-10-31 10:58:09 -04:00

tests

[ty] Limit shown import paths to at most 5 unless ty runs with -v (#20912)

2025-10-16 13:18:09 +02:00

build.rs

Rename Red Knot (#17820)

2025-05-03 19:49:15 +02:00

Cargo.toml

[ty] Some more simplifications when rendering constraint sets (#21009)

2025-10-22 13:38:44 -04:00

mdtest.py

[ty] Set INSTA_FORCE_PASS and INSTA_OUTPUT environment variables from mdtest.py (#21029)

2025-10-22 15:32:14 +01:00

mdtest.py.lock

Rename Red Knot (#17820)

2025-05-03 19:49:15 +02:00