[hauntsaninja]

Fixes #10004

An alternate fix would be to only check the first 100 overloads for overlaps.

[AlexWaygood]

An alternate fix would be to only check the first 100 overloads for overlaps.

I think I'd weakly prefer that? Performance is obviously still very important for us, but it's not as important as it is for pyright, since pyright doubles as a language server. And it feels weird that you might get 50 overlapping-overload errors if you had 99 overloads, but then that number drops to 0 when you added one more overload.

[ilevkivskyi]

Yeah, I don't like silently skipping all checks if there are many overloads. I think we should just limit inner loop to say 100 next items, this way we will check all "nearby" overloads with linear complexity. Also if we hit this limit, we should show an error on the first line saying that some checks were skipped (as we do e.g. for union math). User may then place a single # type: ignore to suppress this warning.

Also we can still always do the implementation completeness check that is linear (and it doesn't affect stubs anyway).

[github-actions]

Diff from mypy_primer, showing the effect of this PR on open source code:

discord.py (https://github.com/Rapptz/discord.py)
+ discord/client.py:1237: error: Not all overload combinations were checked for overlap because there were too many  [performance-limit]

scipy-stubs (https://github.com/scipy/scipy-stubs)
+ scipy-stubs/sparse/_construct.pyi:142: error: Not all overload combinations were checked for overlap because there were too many  [performance-limit]
+ scipy-stubs/sparse/_construct.pyi:1506: error: Not all overload combinations were checked for overlap because there were too many  [performance-limit]
+ scipy-stubs/sparse/_construct.pyi:1628: error: Not all overload combinations were checked for overlap because there were too many  [performance-limit]
+ scipy-stubs/sparse/_construct.pyi:1750: error: Not all overload combinations were checked for overlap because there were too many  [performance-limit]
+ scipy-stubs/sparse/_construct.pyi:1918: error: Not all overload combinations were checked for overlap because there were too many  [performance-limit]
+ scipy-stubs/sparse/csgraph/_laplacian.pyi:57: error: Not all overload combinations were checked for overlap because there were too many  [performance-limit]

[ilevkivskyi]

I think it is fine to merge as is, but what do you think about doing something like I proposed in this comment #20439 (comment)?

[hauntsaninja]

Okay, I implemented that, but it's a little messy so opening it as a separate PR: #22393