11 replies

Currying and Type Restriction in TypeScript

I like to export Equal functions with the type set so I don't accidentally compare two different objects, however I have found it a little awkward in doing so. Am I doing something wrong?

// User.ts

// only gives me the curried version and second param is not restricted to User
export const equals = Equal.equals<User>

// gives me a non-curried version and correctly restricts the input to User
export const equals = Equal.equals<User, User>

// User.ts

// only gives me the curried version and second param is not restricted to User
export const equals = Equal.equals<User>

// gives me a non-curried version and correctly restricts the input to User
export const equals = Equal.equals<User, User>

It would be cool to define it once, have both args restricted to the defined type and have the dual API supported

Effect Community•2y ago•

11 replies

Stephen Bluck

Currying and Type Restriction in TypeScript

I like to export Equal functions with the type set so I don't accidentally compare two different objects, however I have found it a little awkward in doing so. Am I doing something wrong?

// User.ts

// only gives me the curried version and second param is not restricted to User
export const equals = Equal.equals<User>

// gives me a non-curried version and correctly restricts the input to User
export const equals = Equal.equals<User, User>

// User.ts

// only gives me the curried version and second param is not restricted to User
export const equals = Equal.equals<User>

// gives me a non-curried version and correctly restricts the input to User
export const equals = Equal.equals<User, User>

It would be cool to define it once, have both args restricted to the defined type and have the dual API supported

Currying and Type Restriction in TypeScript

Similar Threads

Currying and Type Restriction in TypeScript

Similar Threads

Similar Threads

Similar Threads