no error when using `TypeGuard` outside of return type
Open
Nobody has claimed this yet.
bug
topic-typeguard-typeis
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
from typing import TypeGuard
def foo(value: TypeGuard[int]) -> None: ... # no error
bar: TypeGuard[int] = True # no error
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
Reproduce the two snippets in the linked mypy-play example and begin by reading how mypy handles TypeGuard annotations. Done means diagnostics are emitted when TypeGuard is used in a parameter or variable annotation, while its supported return-type use remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100