Michael Arnaldi

I use fp-ts deeply in any of my projects: - https://www.matechs.com/ - https://www.neob.io/ Reference for the open source framework and set of extensions to the fp-ts echosystem we opensource: https://github.com/mikearnaldi/matechs-effect

By how TS inference work the only pipeable would be: (use, release) => (acquire) => ... to be used like `pipe(doBla, blaBla, bracket(use, release))` That's because `release` needs the types...

I am kind of surprised by this but what seems to be affecting is the suspension of `map`, namely: ```ts export const map: (f: (a: A) => B) => (fa:...

It's not stack safe, `tailRecM` is implemented recursively which means any sync execution will make it unsafe, it is safe when used in combo with task because task is safe

Unless I am missing something it is not stack safe it is a plain recursive function, in tailRec safety is achieved implementing the logic in an iterative manner https://github.com/gcanti/fp-ts/blob/master/src/ChainRec.ts#L73 but...

There are other issues discussing the same thing, the desired behaviour isn't possible, in your snippet Option is both a type and a namespace re-export and unfortunately ts gets confused...

There is a native-looking way by exploiting generators, I go in details about this in the following article: https://dev.to/matechs/abusing-typescript-generators-4m5h The advantage compared to a pipe-based one is you are able...

> @steida: what @SRachamim proposes is indeed a little bit more ergonomic than the current status quo outlined in the comment that you linked too, IMO. Consider that you won't...

it could be `OptionHKT` or `OptionRepr` or similar, at the end it is a generic representation of a type

(overall I agree, it is refreshing how simpler it is)