51 replies

Improving Array Partition with Refined Types

Is there a reason why Array.partition (partition functions in general) when accepting a refinement don't exclude the refined type from the starting type and put the resulting type in the "left" partition?

declare const myarray: (string | number)[]
const result = partition(myarray, Predicate.isString)
// result is [(string | number)[], string[]]
// expected: [Exclude<string | number, string>[], string[]]

declare const myarray: (string | number)[]
const result = partition(myarray, Predicate.isString)
// result is [(string | number)[], string[]]
// expected: [Exclude<string | number, string>[], string[]]

declare const myarray: (string | number)[]
const result = partition(myarray, Predicate.isString)
// result is [(string | number)[], string[]]
// expected: [Exclude<string | number, string>[], string[]]

declare const myarray: (string | number)[]
const result = partition(myarray, Predicate.isString)
// result is [(string | number)[], string[]]
// expected: [Exclude<string | number, string>[], string[]]

Improving Array Partition with Refined Types

Similar Threads

Similar Threads

Similar Threads