-
Notifications
You must be signed in to change notification settings - Fork 469
Adding type annotation to curried function emits compiler error #7544
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
Comments
cristianoc
added a commit
that referenced
this issue
Jun 13, 2025
Fixes #7544 Fix an issue in type checking partial application in the presence of user-defined function types. The type checking code, when extracting the arity of the type annotation given to a function being applied, was expecting a concrete function type instead of looking up a possible type definition.
cristianoc
added a commit
that referenced
this issue
Jun 13, 2025
Fixes #7544 Fix an issue in type checking partial application in the presence of user-defined function types. The type checking code, when extracting the arity of the type annotation given to a function being applied, was expecting a concrete function type instead of looking up a possible type definition.
Good catch. #7548 |
cristianoc
added a commit
that referenced
this issue
Jun 13, 2025
Fixes #7544 Fix an issue in type checking partial application in the presence of user-defined function types. The type checking code, when extracting the arity of the type annotation given to a function being applied, was expecting a concrete function type instead of looking up a possible type definition.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since v12.0.0-alpha.6, adding a type annotation to a curried function gives the error
This function is a curried function where an uncurried function is expected
:(Playground link)
The text was updated successfully, but these errors were encountered: