astral-sh/ruff - CodSpeed

ruff

Blog Docs Changelog

Performance History

Latest Results

claude/protocol-isinstance-checks-JmhEI

12 minutes ago

[ty] Fix Top materialization to respect TypeVar bounds and ignore defaults When computing `Top[Foo]` for an unparameterized generic class, TypeVar bounds were ignored (materializing to `object` instead of the bound) and TypeVar defaults were used instead of the widest possible type. Two fixes applied: 1. In `Specialization::materialize_impl`, cap materialized types by the TypeVar's upper bound when materializing in the widening direction. 2. In `Specialization::materialize_impl`, detect when a TypeVar's value matches its default and replace with `Unknown` for proper widening. 3. In `ClassLiteral::top_materialization`, use upper bounds directly for covariant/bivariant TypeVars via new `upper_bound_specialization`. https://claude.ai/code/session_017dAXrsVcmMYhtL4eTCfPUf

claude/fix-typevar-annotations-BfKAQ

13 minutes ago

claude/protocol-isinstance-checks-JmhEI

23 minutes ago

[ty] Fix Top materialization to respect TypeVar bounds and ignore defaults When computing `Top[Foo]` for an unparameterized generic class, TypeVar bounds were ignored (materializing to `object` instead of the bound) and TypeVar defaults were used instead of the widest possible type. Two fixes applied: 1. In `Specialization::materialize_impl`, cap materialized types by the TypeVar's upper bound when materializing in the widening direction. 2. In `Specialization::materialize_impl`, detect when a TypeVar's value matches its default and replace with `Unknown` for proper widening. 3. In `ClassLiteral::top_materialization`, use upper bounds directly for covariant/bivariant TypeVars via new `upper_bound_specialization`. https://claude.ai/code/session_017dAXrsVcmMYhtL4eTCfPUf

claude/fix-typevar-annotations-BfKAQ

25 minutes ago

[ty] Remove `Copy` implementation from `ConstraintSet`

alex/constraints

39 minutes ago

[ty] Fix Top materialization to respect TypeVar bounds and ignore defaults When computing `Top[Foo]` for an unparameterized generic class, TypeVar bounds were ignored (materializing to `object` instead of the bound) and TypeVar defaults were used instead of the widest possible type. Two fixes applied: 1. In `Specialization::materialize_impl`, cap materialized types by the TypeVar's upper bound when materializing in the widening direction. 2. In `Specialization::materialize_impl`, detect when a TypeVar's value matches its default and replace with `Unknown` for proper widening. 3. In `ClassLiteral::top_materialization`, use upper bounds directly for covariant/bivariant TypeVars via new `upper_bound_specialization`. https://claude.ai/code/session_017dAXrsVcmMYhtL4eTCfPUf

claude/fix-typevar-annotations-BfKAQ

49 minutes ago

claude/protocol-isinstance-checks-JmhEI

51 minutes ago

[ty] Add more test cases for subclass methods autocompletion

leandrobbraga:issue-2858

57 minutes ago

Active Branches

[ty] Detect `isinstance()` and `issubclass()` calls between nominal types and unsafely overlapping `Protocol` types

last run

12 minutes ago

0%

[ty] Use upper bounds for TypeVar materialization in generic classes

last run

13 minutes ago

-8%

[ty] Remove `Copy` implementation from `ConstraintSet`

last run

39 minutes ago

+1%

© 2026 CodSpeed Technology

Home Terms Privacy Docs