9 commits

Author	SHA1	Message	Date
Douglas Creager	dc84645c36	[ty] Use separate Rust types for bound and unbound type variables (#19796) ... This PR creates separate Rust types for bound and unbound type variables, as proposed in https://github.com/astral-sh/ty/issues/926. Closes https://github.com/astral-sh/ty/issues/926 --------- Co-authored-by: Carl Meyer <carl@astral.sh>	2025-08-11 15:29:58 -04:00
Douglas Creager	06cd249a9b	[ty] Track different uses of legacy typevars, including context when rendering typevars (#19604) ... This PR introduces a few related changes: - We now keep track of each time a legacy typevar is bound in a different generic context (e.g. class, function), and internally create a new `TypeVarInstance` for each usage. This means the rest of the code can now assume that salsa-equivalent `TypeVarInstance`s refer to the same typevar, even taking into account that legacy typevars can be used more than once. - We also go ahead and track the binding context of PEP 695 typevars. That's _much_ easier to track since we have the binding context right there during type inference. - With that in place, we can now include the name of the binding context when rendering typevars (e.g. `T@f` instead of `T`)	2025-08-01 12:20:32 -04:00
David Peter	293d4ac388	[ty] Add meta-type tests for legavy TypeVars (#18453) ... ## Summary Follow up to the comment by @dcreager [here](https://github.com/astral-sh/ruff/pull/18439#discussion_r2123802784).	2025-06-04 07:44:44 +00:00
Carl Meyer	ad024f9a09	[ty] support callability of bound/constrained typevars (#18389) ... ## Summary Allow a typevar to be callable if it is bound to a callable type, or constrained to callable types. I spent some time digging into why this support didn't fall out naturally, and ultimately the reason is that we look up `__call__` on the meta type (since its a dunder), and our implementation of `Type::to_meta_type` for `Type::Callable` does not return a type with `__call__`. A more general solution here would be to have `Type::to_meta_type` for `Type::Callable` synthesize a protocol with `__call__` and return an intersection with that protocol (since for a type to be callable, we know its meta-type must have `__call__`). That solution could in principle also replace the special-case handling of `Type::Callable` itself, here in `Type::bindings`. But that more general approach would also be slower, and our protocol support isn't quite ready for that yet, and handling this directly in `Type::bindings` is really not bad. Fixes https://github.com/astral-sh/ty/issues/480 ## Test Plan Added mdtests.	2025-05-30 12:01:51 -07:00
Alex Waygood	d1bb10a66b	[ty] Understand classes that inherit from subscripted Protocol[] as generic (#17832)	2025-05-09 17:39:15 +01:00
Douglas Creager	b705664d49	[ty] Handle typevars that have other typevars as a default (#17956) ... It's possible for a typevar to list another typevar as its default value: ```py class C[T, U = T]: ... ``` When specializing this class, if a type isn't provided for `U`, we would previously use the default as-is, leaving an unspecialized `T` typevar in the specialization. Instead, we want to use what `T` is mapped to as the type of `U`. ```py reveal_type(C()) # revealed: C[Unknown, Unknown] reveal_type(C[int]()) # revealed: C[int, int] reveal_type(C[int, str]()) # revealed: C[int, str] ``` This is especially important for the `slice` built-in type.	2025-05-08 19:01:27 -04:00
Douglas Creager	0d9b6a0975	[ty] Handle explicit variance in legacy typevars (#17897) ... We now track the variance of each typevar, and obey the `covariant` and `contravariant` parameters to the legacy `TypeVar` constructor. We still don't yet infer variance for PEP-695 typevars or for the `infer_variance` legacy constructor parameter. --------- Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> Co-authored-by: Carl Meyer <carl@astral.sh>	2025-05-07 08:44:51 -04:00
Charlie Marsh	a2e9a7732a	Update class literal display to use <class 'Foo'> style (#17889) ... ## Summary Closes https://github.com/astral-sh/ruff/issues/17238.	2025-05-06 20:11:25 -04:00
Micha Reiser	b51c4f82ea	Rename Red Knot (#17820)	2025-05-03 19:49:15 +02:00

Renamed from crates/red_knot_python_semantic/resources/mdtest/generics/legacy/variables.md (Browse further)