overloads_consistency_3 error

Overload implementation is inconsistent with its signatures

When an overload implementation is present the spec requires: the return type of every overload is assignable to the implementation's return type, and the implementation's parameter types are assignable from every overload's parameter types (the implementation must accept them all).

To remain false-positive free this only compares **known primitive types** (int/str/bytes/float/bool/complex/object/None and unions of them). Any TypeVar, generic (listint), Callable, or otherwise non-primitive annotation is skipped, since text-level assignability cannot be decided for it.

How to handle it

Every rule is on by default — strict is the default, not a cage. You can dial overloads_consistency_3 down per-file or per-path from your editor or pyproject.toml, or fix the code so it type-checks. See the Type System rules and the complete diagnostic reference.

Canonical URL: https://www.basilisk-python.dev/errors/overloads_consistency_3