Skip to content

Improve Step 5 of overload call evaluation.#2250

Open
rchen152 wants to merge 1 commit intopython:mainfrom
rchen152:overload
Open

Improve Step 5 of overload call evaluation.#2250
rchen152 wants to merge 1 commit intopython:mainfrom
rchen152:overload

Conversation

@rchen152
Copy link
Copy Markdown
Collaborator

@rchen152 rchen152 commented Apr 8, 2026

Makes two modifications to step 5 of overload call evaluation:

  1. When materializing arguments to check whether we can eliminate overloads, skip arguments that have the same parameter type in all overloads.
  2. When we still have multiple overloads after the materialization filter, try to find a return type that all materializations of all other return types are assignable to.

Updates the conformance tests as well. All type checkers already do (1). Mypy and pyrefly pass the conformance test for (2). I believe mypy has a heuristic that approximates the new rule; pyrefly implements it exactly. I updated pyrefly to a version that contains its implementation of (2), which also picked up some unrelated changes.

Makes two modifications to step 5 of overload call evaluation:
1. When materializing arguments to check whether we can
   eliminate overloads, skip arguments that have the same
   parameter type in all overloads.
2. When we still have multiple overloads after the materialization
   filter, try to find a return type that all materializations of
   all other return types are assignable to.

Updates the conformance tests as well. All type checkers already do
(1). Mypy and pyrefly pass the conformance test for (2). I believe
mypy has a heuristic that approximates the new rule; pyrefly
implements it exactly.
@carljm
Copy link
Copy Markdown
Member

carljm commented Apr 8, 2026

I think it's preferable to keep PRs updating type-checker versions separate from PRs implementing conformance suite and spec changes.

- All possible :term:`materializations <materialize>` of the argument's type are
assignable to the corresponding parameter type, or
- The parameter types corresponding to this argument in all of the remaining overloads
are :term:`equivalent`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is correct but there's some subtlety in the wording that we should cover in the test cases:

  • "The parameter types corresponding to this argument". That may be a very different parameter in each of the overloads; e.g. maybe one takes *args and the other has explicit arguments. So my reading is that to check this, you have to create for each overload a mapping between argument and parameter type, and consult that. What is the parameter type corresponding to an unpacked argument, though?
  • "the remaining overloads". So we only check this overload and all following overloads, not ones above it?

def example5(x: A[Any]) -> A[Any]: ...

def test(x: Any):
# Steps 5 eliminates the first overload because there exists a
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Steps 5 eliminates the first overload because there exists a
# Step 5 eliminates the first overload because there exists a



@overload
def example8(x: str, y: Literal['o1']) -> str: ... # E? some type checkers report unsafe overlap between example8's overloads
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This unnecessary complexity would be eliminated (without reducing the strength of the test) by changing str here to bool (and changing the rest of the test accordingly).



def check_example9(x: Any):
# Steps 5 eliminates the first overload because there exists a
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Steps 5 eliminates the first overload because there exists a
# Step 5 eliminates the first overload because there exists a

@srittau srittau added the topic: typing spec For improving the typing spec label Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic: typing spec For improving the typing spec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants