-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
signal/slot patternmaking function signatures generic #5115
Comments
It looks like I accidentally submitted this issue long before I was done editing, so if you got it by email you should click the link to the issue. Sorry! |
I don't know if this fixes your problem, but don't you want |
Yes, it is invalid, but that's part of the problem in terms of expressive limitations. I don't want to limit |
This is a duplicate of python/typing#264 (you can cast your vote in favour of special |
I'm trying to design a simple signal/slot package that is pep484-compatible, but it's proving trickier than I thought. The problem is that the type-checked signatures of the generic class's methods should vary depending on its parameterization.
Here's a naive rough draft:
Any advice on the best way to proceed is greatly appreciated, esp. any low-hanging issues that could unlock this functionality.
Related to #4031
edit: removed
emit
method in favor of the callable's__call__
methodThe text was updated successfully, but these errors were encountered: