33 replies

Need for Higher Kinded Types in Composing Refinements

I was looking at composing refinements, but noticed that there's no real way of accomplish the following without HKT right?

const hasPropertyWith: ... = (v, p, refinement) => Predicate.hasProperty(p)(v) && refinement(v[p])
const hasPropertyNotNull = hasPropertyWith(Predicate.isNotNull)

const hasPropertyWith: ... = (v, p, refinement) => Predicate.hasProperty(p)(v) && refinement(v[p])
const hasPropertyNotNull = hasPropertyWith(Predicate.isNotNull)

const hasPropertyWith: ... = (v, p, refinement) => Predicate.hasProperty(p)(v) && refinement(v[p])
const hasPropertyNotNull = hasPropertyWith(Predicate.isNotNull)

const hasPropertyWith: ... = (v, p, refinement) => Predicate.hasProperty(p)(v) && refinement(v[p])
const hasPropertyNotNull = hasPropertyWith(Predicate.isNotNull)

Cause

Predicate.isNotNull

Predicate.isNotNull

Predicate.isNotNull

Predicate.isNotNull is (correctly) typed as:

<A>(input: A): input is Exclude<A, null> => input !== null

<A>(input: A): input is Exclude<A, null> => input !== null

<A>(input: A): input is Exclude<A, null> => input !== null

<A>(input: A): input is Exclude<A, null> => input !== null

Which means

should be set later on, while it's always set immediately when creating the

hasPropertyNotNull

hasPropertyNotNull

hasPropertyNotNull

hasPropertyNotNull refinement. Is it correct?

Need for Higher Kinded Types in Composing Refinements

Similar Threads

Similar Threads

Similar Threads