Repository navigation
Tuple elements remain optional after an any() None check #5434
Description
Describe the Bug
After checking that no tuple element is None, Pyrefly still treats the tuple elements as optional:
def pair(
first: int | None,
second: str | None,
) -> tuple[int, str]:
values = (first, second)
if any(value is None for value in values):
raise ValueError("missing value")
return valuesI expected Pyrefly to infer values as tuple[int, str] after the guard. Instead, it reports:
Returned type `tuple[int | None, str | None]` is not assignable to declared return type `tuple[int, str]` [bad-return]
Environment: macOS 27.0.1, Pyrefly 1.4.0, Python 3.15.2 (CLI).
Activity
1-DARK commentedon Nov 2, 2026
#claim
github-actions commentedon Nov 2, 2026
@1-DARK you've claimed this issue — it's now assigned to you. Thanks for picking it up! 🎉
Narrow tuple elements after any()/all() None checks (meta#5484)