Now *CustomType and **CustomType arguments are properly checked - #11151
Conversation
**CustomType argument is properly checked*CustomType and **CustomType argument is properly checked
*CustomType and **CustomType argument is properly checked*CustomType and **CustomType arguments are properly checked
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
JukkaL
left a comment
There was a problem hiding this comment.
Nice, this was a pretty bad gap in type checking. Left a few comments (not a full review).
|
Ok, I am adding #11138 support, it will require a couple of hours. |
|
@hauntsaninja any ideas why |
|
Just pushed a fix... @msullivan 's hack for edgedb in mypy_primer ended up breaking |
|
@hauntsaninja thank you! 🚀 |
|
@JukkaL @hauntsaninja is there anything else I can do to get this merged? Today we got another bugreport about this: #11375 |
hauntsaninja
left a comment
There was a problem hiding this comment.
Thanks, this is great!
Wish it was nicer to get the mapping and iterable types
|
This PR fixed an issue in an internal repo that I just encountered when testing the 0.920 release |
|
Awesome! 🎉 |
The thing about this patch is that
ArgTypeExpanderneededmapping_typeanditerable_typefor checking*and**arguments.But, this context was not provided.
I've also fixed a bunch of related
TODOitems.Closes #11144
Closes #11138
Closes #11375