TypeVars should be allowed to be the same
Open
Nobody has claimed this yet.
documentation
priority-0-high
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Two unbound TypeVars A and B can potentially be the same:
from typing import Callable, Iterable, TypeVar
A = TypeVar("A")
B = TypeVar("B")
def identity(x: A) -> A:
return x
# ok
def _map(queue: Iterable[B], function: Callable[[B], A]) -> Iterable[A]:
return map(function, queue)
# fails
def _map2(queue: Iterable[B], function: Callable[[B], A] = identity) -> Iterable[A]:
return map(function, queue)
The introduced default keyword argument leads to the following unexpected error:
error: Incompatible default for argument "function" (default has type "Callable[[A], A]", argument has type "Callable[[B], A]")
I'm using mypy 0.740.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the two _map examples from the issue and compare how mypy checks the default Callable[[A], A] against Callable[[B], A]. Trace the type-variable compatibility and default-argument checking involved. Done means _map2 is accepted and the reported incompatibility has a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100