This is another case of what we like to call “death by a thousand overloads”, and it doesn’t even solve the problem generally. It only gives correct types for as many overloads as we care to write.
Basically they support a rest operator now that make it unnecessary to have the many overloads of pipe and compose we currently have.
Is it realistic to bump to a breaking change in this repo to support Typescript 4? It might solve some of the other ways ramda and typescript don't play nice.
So typescript 4 is out, and its headline feature is almost like it's made specifically for ramda.
https://devblogs.microsoft.com/typescript/announcing-typescript-4-0/#variadic-tuple-types
Basically they support a rest operator now that make it unnecessary to have the many overloads of
pipe
andcompose
we currently have.Is it realistic to bump to a breaking change in this repo to support Typescript 4? It might solve some of the other ways ramda and typescript don't play nice.