Alex Waygood

> However, it conflicts with ruff's ARG002. If a parameter is unused, it will add an underscore prefix or directly use _, for example in a subclass method inheriting from...

> (please feel free to close this issue) Instead, I'm going to repurpose the issue, since we don't currently have an issue open to track improving the quality of our...

> What is the status on this? Would be really useful to have! The first PR for this is now up: https://github.com/astral-sh/ruff/pull/21436

@vlashada our Liskov checks are working as intended here. Currently, we view any function lacking an explicit return-type annotation as implicitly returning `Any`/`Unknown` (the two concepts are equivalent), and `Any`/`Unknown`...

@Paul-B98, one option you might consider is to make your abstract base class generic, e.g. ```py class A: pass class B(A): pass class Abstract[T: A]: def test(self, state: T) ->...

> Moving this to GA because we feel the current feature-set is adequate for beta (though it would be nice to add a few more things if we have time)....

> Currently this type-checks on the playground (I don't know whether it also type-checks on main): (The ty playground automatically gets a fresh deploy on each new commit to `main`,...

anyway: we're working on `TypedDict` features actively, and we will get an improved `TypedDict` assignability implementation delivered to you as soon as we can 😄

We infer a more precise type than `type[str]`. `type[str]` is "the class object `str`, or any subclass of that class". ``, on the other hand, is a singleton type. It...

This assertion passes ty, but I don't know if it passes other type checkers: ```py assert_type(type("") is str, Literal[True) ``` But yeah, we may want to consider proposing something like...