-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Expected type during value synthesis #74
Comments
7 tasks
Added the parameter-argument part with ezno/checker/src/types/calling.rs Lines 53 to 98 in 1aa77e2
Not great position + overhead of clone. But works ATM These work though |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the
mapper
functionsa
parameter is synthesised as genericthen the function is checked based on the restriction.
A better way would be to synthesise the function with the knowledge/expectation that it is expected to be a function as
number => U
. This means that thenew_function
can then create parameter restrictions eagerly.This could be considered as traditional type inference
The text was updated successfully, but these errors were encountered: