[red-knot] Move relation methods from CallableType to Signature
#17365
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR moves all the relation methods from
CallableTypetoSignature.The main reason for this is that
Signatureis going to be the common denominator between normal and overloaded callables and the core logic to check a certain relationship is going to just require the information that would exists onSignature. For example, to check whether an overloaded callable is a subtype of a normal callable, we need to check whether every overloaded signature is a subtype of the normal callable's signature. This "every" logic would become part of theCallableTypeand the core logic of checking the subtyping would exists onSignature.