Skip to content

Typescript 4: Solve a lot of our problems #448

@ranneyd

Description

@ranneyd

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

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions