-
Notifications
You must be signed in to change notification settings - Fork 116
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
Support support context bounds on FunctionDef
s
#258
Comments
Yes, we need to fix this. It's a big usability problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are lots of
FunctionDef
s that should work for multiple types specified by existing parameter bounds e.g.it would be good to be able to do something like:
This doesn't work because we're using the FunctionDef syntax class - the type of the argument passed to the
apply
method on the returnedFunctionCall
is not known whenSign
is called, meaning we have to specify the type when calling the function and explicity call apply which is not exactly a nice nice UXthis issue was discovered from some work with @saucam & @brbrown25 on other functions
The text was updated successfully, but these errors were encountered: