Flow port

Flow offers things like $Call which have been a bottleneck for me so far. I should finish up my flow branch to get things up to parity. I’m not actually good at Flow so help welcome!

edit: I should check type-at-pos to find the inferred types.

[KiaraGrouwstra]

@goodmind: you’re not far off! it has two use-cases:

• pattern matching, within TS now covered by conditional types;
• calculating types based on an input function, needed for e.g. map on tuples / heterogeneous objects (both already covered in Flow utilities), as well as for e.g. function composition and currying.

This is why I was kinda sad they gave us conditional types instead of $Call, as it means the second use-case is likely still gonna remain pretty far off. And since those are pretty vital for FP libs like Ramda, that’s why I’d feel more optimistic about Flow at this point.

[KiaraGrouwstra]

whoa, that’s pretty nice! It’s felt like the TS team has been fairly swamped with stuff, though at least recently Ramda got some attention there as it was the only typing repo convoluted enough to break on their recent changes. 😂