[red-knot] check call arguments #14161
Comments
This was referenced Nov 7, 2024
carljm
added a commit
that referenced
this issue
Nov 13, 2024
When we look up the types of class bases or keywords (`metaclass`), we currently do this little dance: if there are type params, then look up the type using `SemanticModel` in the type-params scope, if not, look up the type directly in the definition's own scope, with support for deferred types. With inference of function parameter types, I'm now adding another case of this same dance, so I'm motivated to make it a bit more ergonomic. Add support to `definition_expression_ty` to handle any sub-expression of a definition, whether it is in the definition's own scope or in a type-params sub-scope. Related to both #13693 and #14161.
carljm
added a commit
that referenced
this issue
Nov 14, 2024
## Summary Add a typed representation of function signatures (parameters and return type) and infer it correctly from a function. Convert existing usage of function return types to use the signature representation. This does not yet add inferred types for parameters within function body scopes based on the annotations, but it should be easy to add as a next step. Part of #14161 and #13693. ## Test Plan Added tests.
carljm
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: