Generic types with currying about npm-ramda HOT 5 CLOSED

You could consider making type hasKey generic:

export type hasKey<T> = R.CurriedFunction2<String, T, boolean>

from npm-ramda.

I had thought to try that as well and while it does solve the issue in the type definition, it creates another issue in the assignment of the type to the variable declaration. Since T isn't declared until the lambda, it can't be used to type the variable. The best I've found so far is to use the generic type in the type definition and use Function for the type of the variable declaration, although this is also not ideal. Any other thoughts?

from npm-ramda.

Hmm, I have to think about this a bit longer. Did your read the gist of @waldogit and my own write-up about currying? Maybe that will give you some clues.

from npm-ramda.

I think the definition of const hasKey is flawed because a const is not allowed to change but here its type is defined as a generic. I think when defining const hasKey you need to specify T.

from npm-ramda.

@patrickjtoy, can I assist in any way? Otherwise I'll close this issue.

from npm-ramda.