Compose definitions

[lax4mike]

Hello!

I was messing around with compose and discovered something interesting. The type definitions for compose are almost identical to pipe (only the function order is reversed), but it doesn't seem to behave the same. Consider these compositions, one with compose and one with pipe:

const poo = R.compose(
  R.defaultTo('fallback'),
  R.nth(1)
)([1, 2]);

const poo2 = R.pipe(
  R.nth(1),
  R.defaultTo('fallback')
)([1, 2]);

pipe is fine with this, and poo2 is correctly string | number. On the other hand, compose is getting confused and says poo is unknown. Additionally, there's a big red squiggle under R.nth(1) complaining about the unknown.

Given that the type definitions are almost identical, I'm not sure why compose wouldn't work the same as pipe. Any idea what's going on here?

[Harris-Miller]

That is very odd. Stranger still that if you put a R.toString at the "end" of either, they both then work as expected

See here

[lax4mike]

Adding toString at the end makes sense to me because the signature is unknown -> string so it would return string no matter what, essentially masking the unknown error that compose introduced.

[lax4mike]

I'm reaching out for some help on discord. It looks like someone else had this question before and there was no resolution 🫤

[lax4mike]

I also posted on stack overflow, hopefully someone can help us!

[lax4mike]

I also cross posted to ramda/ramda