- Agreed the word type here is ambiguous but yes I did mean the same type as the TypeVarLike (TypeVar defaults have to be TypeVars, etc.). - Yes, `T1 = TypeVar("T1"), T2 = TypeVar("T2", default=list[T1])` should work. - Yes, TypeVar scoping should allow for that. - For this case, I was just concerned about having to insert placeholder nodes that would cause deadlocks finding TypeVar names. After looking into mypy it seems fine there, so I'd assume type checkers are fine with any order. - Yeah exactly right if T1 has a solution but T2 doesn't, the constraint solver should use the type of T1 as T2, I don't think the converse makes sense but I'm happy to be proven wrong on this. I'm currently working on the mypy implementation of this feature (https://github.com/Gobot1234/mypy/tree/TypeVar-defaults) and have most of the TypeVar features working on my local version of the branch I'm just working on squashing some bugs. I'll send a PR to python/peps to fix the wording issues as soon as I can. Thanks!