-
Notifications
You must be signed in to change notification settings - Fork 89
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
Currying and TypeScript #548
Comments
Unfortunately, there is nothing much to share. I was subscribed to variadic functions Typescript issue so I have the change to play very early on with variadic tuple types. I also read all the discussions and examples around it in the hope that I will be able to use it in Rambda. As much as I tried, I couldn't make it work. I have the impression that this feature alone is not enough and further features are needed in order to receive proper R.curry/R.compose definitions. Now, there is not much I can do, so I am just hoping that maintainers of |
Ok, I got the situtation, thanks for sharing! I discovered, for myself, that I'm fine with Guys from https://github.com/sanctuary-js/sanctuary came to the same conclusion and now I certainly see how. |
I, myself barely use |
Sure, I don't mind, I only wanted to ask your opinion. |
I'm a Typescript newbie... As it seems,
R.curry
function does not preserve typing at all (returningany
). I suppose this is due to TypeScript limitations on generics and variadic args. Would be great if you enlighten us on the current status quo of this topic.Looks like TypeScript 4 has all the ingredients for generic
curry
. Are you going to update as it leaves beta?Are there some workarounds to make curried and strictly typed functions (with or without
R.curry
) right now?The text was updated successfully, but these errors were encountered: